HNHacker News
TopNewBestAskShowJobs

johnydoe

13 karma · joined January 17, 2024

submissionscomments
johnydoe··on Ask HN: Arc is dead, where should we move now?
I’ve been using https://sigmaos.com/ for the past couple of years, and it works very similar
johnydoe··on How to establish a remote connection from Linux to Mac?
What do you mean by remote connection? Do you want to transfer files? Do you want to stream and control the GUI? Something else? In the first case, SSH is probably the best solution. In the latter case, something like VNC might work across all platforms.
johnydoe··on Dutch suburb where residents must grow food on at least half of their property
I actually live in this area, so imagine my surprise to see a guardian article about my little neighborhood, and it being posted on HN!
johnydoe··on Ask HN: Best Minimal Blog Site?
Prose.sh is as minimalist as you can get it
johnydoe··on FacePoke – Upload a facial photo, click to adjust facial expressions
No terms of service, no privacy policy (both are dead links), and nowhere is it mentioned why this is free or what happens with the uploaded files. Couple of red flags to me right there
johnydoe··on Hetzner lowers pricing of Intel cloud servers
I’m not familiar with their original pricing, can anyone list the changes?
johnydoe··on GitHub wants to know where you live by 19 Aug 2024
…if you live in the US.
johnydoe··on Ask HN: Alternatives to the email masking service Firefox Relay?
There’s https://simplelogin.io/, which is owned by Proton now, so similar in terms of privacy. You can get it separately, or as part of Proton Pass or Mail
johnydoe··on Ask HN: Devs: Do you find any value in Arrange, Act Assert comments in tests?
Same here, it gives me structure if the amount of arrange code is large. It also gives me structure when writing, as it can sometimes be very tempting to mix act and assert statements
johnydoe··on Ask HN: Scrum <–-> Kanban
When I started at my current company 2 years ago we were doing a rigid form of scrum. Over time, I’ve been able to bend that with my teams towards something that works for them and the product they are working on, instead of the other way around. What we ended up with is closer to Kanban; we stopped sprints and sprint planning and replaced it with WIP rules, and pulling work on the board when needed. We refine stories as needed, which means we don’t spend more time in meetings than we absolutely have to to gain alignment. We've retained things from scrum we deemed useful, like the retrospectives, and some sort of regular alignment with stakeholders. Altough not part of scrum or kanban, we’ve exposed engineers more to customers, instead of internal stakeholders, which means the solutions we’re making are much closer to what customers actually need vs what a stakeholder thinks they need. Overal, the feedback from both engineers as well as stakeholders has been very positive, citing less meetings and more time to make an impact, as well as faster time to impact.