What a sentence to read here.
1,367 karma · joined February 22, 2016
http://nickolinger.com
It's been a while since I've written more than anything trivial in golang, but this seems like a big deal to me. As in, I can define a struct that is consistent and reusable in other structs
As an aside, I have to use Cloudlare at work and it’s a pretty awful experience for the medium sized org I’m at. “Hostile UX” is a common complaint. Maybe they should invest money in competing with Vercel on UX/DX instead of acquiring open source projects.
Your level of fluency would be incredibly rare, and I’ve never seen any Japanese person use romaji in casual online conversation.
“Gunma Banker Mode” would 1) be an insane commute to Tokyo where most banking occurs 2) is strange for someone who says they’re not a programmer, but a banker who is “switching their OS.”
Lastly, your comments just stink of AI because you point the obvious out in not—so-correct ways. “Code” is not the context, but I can see how HN could be reduced to that.
If both are true — this is an AI article and people are commenting with AI, then I fear peak dystopia is upon us and HN is losing its magic to information pollution. Sad times
The article isn’t about writing production ready agents, so it does appear to be that easy
On the other hand, there does seem to be a sleight of hand with Vercel. They want it both ways — to be a company that champions and fosters open source while also keeping the necessary friction in place to make their hosting platform the best choice.
For better or worse, I think we’ll only see more of this model in the future.
I post infrequently but try to keep it interesting
Talk excerpt talking about Angular directives ~8 years ago! https://youtu.be/lGdnh8QSPPk?t=275
I took unemployment.
Positive benefits: I mellowed out, started having more patience, and could see how a big source of burnout was how attached my ego was to my work.
I started working on a link shortener a couple of months ago. Despite it being a hobby project that a lot of folks undertake, building something resilient that is somewhat well-designed is a lot of work. Biggest benefit: I started looking at programming as more of something that I'm capable of instead of my self worth / value on display in pull requests.
> Did you return to your old job?
Nope.
> Would you have done anything differently?
More routine. It's liberating to be able to do what you want, as you want, but I would posit that a majority of humans thrive on routines.
> Is there anything bad out of the sabbatical that you didn't expect?
Friends and family being concerned for my well-being despite my spirits being much higher
Admittedly, it's pretty hard to roll your own DDoS. If I was on bare metal or a service that doesn't provide its own DDoS protection, I would absolutely use something like Cloudflare despite all of the downsides.
Perhaps, what is most interesting is that it took nearly 4-5 years for the front-end community to collectively come to the conclusion that SPAs are not _always_the answer. I don't think the zeal for SPAs came from a bad place either. I can remember how poorly ASP.NET and other frameworks of the 2008-2012 era packaged an overcomplicated way to pass data to view layers. There's lots of curmudgeon-ining from non-frontend folks but, in my opinion, the lack of performance and ergonomics with existing frameworks, combined with the newness of Node.js is what brought about the explosion of tooling and frameworks.
There is a place for SPAs, though. VS Code, Spotify, and other apps that need a desktop / browser experience to feel like a mobile app are great candidates. Twitter, for example, shouldn't be a SPA or SPA-like application. I find that it frequently over-caches content and will randomly refresh my feed at times while I'm browsing. It feels as if a simple web page that needs to deliver more JSON responses as I scroll is trying to do too much.
Ruby ~Rails~ found the middleground where major/minor versions[1] typically land in December. Rails[2] typically follows which gives users ample time to upgrade along with a migration guide
As an aside, Staff Engineers have to ride this strange line of being tech leads, managers, architects, and ICs. In my experience, one part or all parts will suffer. Will Larson's book[1] dances well around the ambiguity, but basically when you take a Staff Engineer job, it'll be unclear what you're signing up for.
There's also a neat changelog https://puter.com/app/changelog
This brings up a really interesting question. If a person or business builds a brand, and another person or company fraudulently uses that brand as a form of promotion and trust building by proxy, is the brand liable for the fraudulent companies behaviors?
This is such a nuanced problem because there's plenty of "snake oil"[2] pushed by celebrities and influencers (Dr. Oz[3] comes to mind), just not at the scale that FTX did. If the court sides with the plantiff, it will set a very interesting precedent where anyone promoting a company will somehow have to do their due diligence. In the case of FTX, I don't know how you would do that research and it seems you would be signing up for accepting liability in the case that the company is fraudulent.
1 - https://www.youtube.com/watch?v=HPM6rf0-e6M
2 - https://en.wikipedia.org/wiki/Snake_oil
3 - https://www.cnn.com/2014/06/17/health/senate-grills-dr-oz
If you have a language or project as complex as Zig and can provide Andrew with some sort of guidance on better implementation / OSS issue management, I would love to see this. Otherwise, I would encourage you to not post comments criticizing work which you're not qualified to criticize.
If anything, this will allow for some meaningful competition