adrianomartins
📅 Joined in 2013
🔼 989 Karma
✍️ 176 posts
Load more
(Replying to PARENT post)
I’m not saying publishers can get away with anything with a simply “beta” label, but it’s an important fact to mention if you’re going to release a whole piece about this…
(Replying to PARENT post)
(Replying to PARENT post)
Show HN:
"The missing linter for Pull Requests"
- Identify problems on pull requests as soon as they become a problem (Waiting for review, long-lived, large, stale, etc) - Automatically notify the stakeholders to take action over the identified problems - Customizable checks for your organization needs - A single configuration for all the repos(!)
I'd love to have your thoughts!
(Replying to PARENT post)
(Replying to PARENT post)
I also 100% agree with what you say about product updates, I want my backup provider to be relatively static and slow in changing their product as long as it is robust and it does the job.
On the more specific reasons I think Backblaze is a little far behind in UI/UX: - It's very hard (or impossible) to know if you're 100% backed up after you add new files to your HD. - When you go to the website to check if your new files are backedup, the web page is extremely slow and outdated (I'm talking windows xp style interface iframed into a modern page). - When you get a new HD, because you're constantly filling this things up, the transition process is very sketchy, to say the least. Technically you go through the same process as when you loose an HD, which might make sense, but the process is very slow and the user doesn't get much feedback as to the progress and state of it. Which is particularly nerve-racking when you're dealing with a huge and priceless treasure trove of information.
That said I do have to make a caveat in favor of Backblaze. Not only it is reasonably priced (100$/year, new pricing), Backblaze seems to be design to run continuously on computers with lots of storage and with their HDs connected at all time. That's why they don't bother giving the information about the completeness of your backup, or even making a good web UI for it, because I guess their target user just turns on Backblaze and never really looks back at it. And forget about sharing files through Backblaze, it is 100% a backup tool, not a modern cloud file tool.
It should be said that I fall a bit off their target user, I want to backup my external drives that are connected only when I add new files, and not my whole computer, all the time. This is also the motivation to once in a while look for an alternative in hopes of finding a better solution.
Thanks for the tip on SpiderOak, I'll have a look into it.
Ask HN:
"Alternative to Backblaze"
(Replying to PARENT post)
(Replying to PARENT post)
(Replying to PARENT post)
Ask HN:
"Tool to record screen and system audio and mic"
(Replying to PARENT post)
Indeed, merge policy management and enforcement is a pain point for a lot of companies out there, specially for the ones growing up and trying to keep a solid process with new people coming in.
Show HN:
"Advanced pull request merge protection for GitHub"
Here's a sneak peek into what you can do with Reviewpad Protect: - Setup branch protection effortlessly with Reviewpad to secure the merge button. - Onboard new developers faster by requiring approvals from senior team members. - Strengthen security with sequential approvals based on authorship and change sensitivity. - Implement code freezes with ease by programmatically blocking merges. - Enforce best practices automatically, ensuring adherence to git conventions. - Guarantee checklist completion by mandating every task to be checked off. - Ensure green CI checks before merging, based on pull request changes. - Centralize merge protection rules, configure once, and apply across all repositories in one place.
Don't leave your codebase vulnerable to subpar merges!
(Replying to PARENT post)