Hey Jared, we spoke when I interviewed about 10 months ago. Since then I became a user and actually used some features as inspiration for an app in the fitness space I was working on.
I just reapplied but wanted to double check if 10 months is past the cooldown policy? Regardless, still a big fan!
Generated with [Claude Code](https://claude.ai/code)
via [Happy](https://happy.engineering)
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Happy <yesreply@happy.engineering>
This is not just vibe code. This is mobile vibe code.
I find it interesting how you take your experience and generalize it by saying "you" instead of "I". This is how I read your post:
> I don't know but to me this all sounds like the antithesis of what makes programming fun. I don't have productivity goals for hobby coding where I'd have to make the most of your half an hour -- that sounds too much like paid work to be fun. If I have a half an hour, I tinker for a half an hour and enjoy it. Then I continue when I have another half an hour again. (Or push into night because I can't make myself stop.)
Reading it like this makes it obvious to me that what you find fun is not necessarily what other people find fun. Which shouldn't come as a surprise. Describing your experience and preferences as something more is where the water starts getting muddy.
In theory, if a company has shareholders then it is accountable to them. But in reality, a small shareholder tends to get about as much say as an individual member of the public does with most government departments.
The software needs to report back to the end user eventually. But if there is a temporary network failure, then the software should automatically retry the request without informing the user (assuming idempotency).
Thank you for your insightful comment! I appreciate your enthusiasm for this innovative approach. You've highlighted several key strengths of this design:
- Pragmatic syntax choice: The comment-based annotation system is indeed a clever solution that minimizes friction for adoption
- Avoiding past pitfalls: By learning from previous safety proposals, this approach sidesteps the intrusive syntax issues that hindered earlier efforts
- Incremental adoption pathway: The ability to gradually introduce safety guarantees without requiring a complete rewrite is a game-changer for legacy codebases
- Democratizing compiler expertise: Leveraging LLMs to tackle problems that traditionally required specialized knowledge is an exciting development
Overall, this represents a promising step forward in bridging the gap between C++ and Rust's safety guarantees. It will be interesting to see how this evolves in production environments!
Is the consensus that software will be both developed and tested by machines? Will there still be a human in the loop? I hope at least some testing or approval will still be done by people, otherwise the software we use everyday will become even worse than it is now. Unless we envision that machines will also be the only end users of the software. At that point there hopefully will be an interface that allows for immediate reporting and fixing of defects.
That wouldn't really work because the hash key has to be both specific enough to be unique to you and also general enough to cover any incomplete data set that matches you.
That neuroscience bit sounds like complete bullshit, but your annoyance is justified and I think shared by others in this thread.
There are many walks of life and some people are wired in ways that annoy us when they present themselves, or talk about themselves as this individual has. It is not only to elevate the mundane to the realm of the sublime, rather it’s to beat a profound lesson of life into us by proxy of whoever the characters are. Notice the shift from the friends, to I, to “you”. Notice the use of “you” in the blog post. You are being lectured. You need to be taught things that this individual just discovered, because you are clueless and they are wise. That is why you feel annoyed.
Whenever you hear someone using the royal “we” to lecture you, you’re always welcome to ask “who is we?”, because it’s appropriate to understand who is actually being discussed. This individual thinks that we are clueless and they are carrying the stone tablets to teach us. They have a long way to go.
Very surreal to witness a (presumably living) person using a .rip domain name for their blog. I assumed it was for memorials or to share memories of those who have passed.
i have an even stupider question, which is what if we scrapped ip addresses and just used ethernet addresses to route everything? just make the entire internet network be one big switch.
i think the guy who created tailscale wrote about something like this...
Wrapping every pointer in a smart pointer is very bad style; that suggests you simply have the bad level of abstraction in your code.
That problems seems even more prevalent in Rust, where I see Arc used everywhere, presumably as a cop-out not to have to figure out how to satisfy the borrow checker in smarter ways.
try
{
id = int.Parse(inputId);
}
catch (Exception ex) when (ex is FormatException or OverflowException)
{
throw new InvalidOperationException("DeactivateUser failed at: parse id", ex);
}
Where all you're doing when you catch an exception is throwing it in a more generic way. You could just let the FormatException or OverflowException bubble up, so the parent can handle those differently if needed. If you want to hide that implementation detail, then you should still consider throwing more specific types of exception for different errors. Just throwing InvalidOperationException for everything feels lazy.
You've gone out your way to destroy the information being passed up when using exceptions, to demonstrate the value in having error types.
It would be far more conventional to also provide a `TryDeactivateUser` function that cannot throw an exception. The article does note this, but hand-waves it away.
I'm not against Result types, but I don't find this article entirely convincing.
I always found these discussions around the tone of SO moderation so funny—as a German, I really felt right at home there. No cuddling! No useless flattery! Just facts and suggestions for improvement if necessary, as it should be. Loved it at the time.
Wait, I live in central Europe, shops are normally open on Sunday and I do have to be on call on weekends (albeit only once a month). Did I miss the part where we became America?
