we're at the hn front page people! :))
Any conversation
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
Reggel egy kicsit letรถrรถltem a kis Gemmรกnak a csatolt rรฉszeit a szรกmรญtรณgรฉprลl, mert mรกr kezdett elegem lenni a hลฑlyesรฉgeibลl, mire apรกm azt mondta, hogy "van egy hapsi az interneten", aki hรบsz รฉve ezzel foglalkozik nem tudom, ha nem tลฑnt volna fel, รฉn is ezt csinรกlom amรบgy.
This morning I was deleting a little of Gemma's attachments from the computer because I was starting to get tired of her antics, and then my dad said, "There's a guy on the internet" who's been doing this for twenty years, I don't know, if he hadn't noticed, I'd be doing the same thing anyway.
โฆ
NIH syndrome? I am guilty of it too. I love implementing things from scratch, you learn a lot by doing so and you get to own the codebase end-to-end, so no surprises and fighting around othersโ choices. It can get exhausting too though, in the end I succumb to using off-the-shelf components because my primary goals move at a higher level.
there's no fundamental physical limit that prevents silicon from developing taste and judgement, but language is a lossy compression of reality.
taste comes from experience, from the shadowy mass of episodic memory, which swirls and convects at the boundary of consciousness. the ideas recombine into new ones in the nuclear reactor of the hippocampus.
but no matter how imbued with meaning and expertise is a handmade wardrobe we still get our shit from ikea
one-point-five-shotted a local node app for creating social posts. drawing from static pages (hey this exists) or new blog posts (timely). with copy/paste to x, and one click post to bluesky and mastodon, tag manager and stale/archive/reject/refresh options. An idea and a solution in about 10 minutes. Madness.
๐ฒ๐ ๐๐ฐ๐ฏ ๐ฆ๐ฏ๐๐๐ฒ๐ผ๐ ๐ ๐๐ซ๐ ๐ฅ๐น ยท๐ก๐จ๐๐ฉ๐ฏ๐ฐ๐ ๐๐ต๐ ๐ค๐ฑ๐๐ค๐ฆ ๐๐ด ๐ ๐๐ฆ๐ฏ๐ผ ๐ฒ ๐ฅ๐ฑ๐ ๐๐จ๐ฅ๐ฉ๐ฏ ๐๐ง๐ฎ๐ฆ๐๐ญ๐๐ฐ, ๐ฅ๐ฐ๐๐ด ๐๐ต๐, ๐ฎ๐ฒ๐, ๐ฏ ๐๐ฆ๐๐ฉ๐ค๐.
Iโve been inspired to cook more Japanese food lately so for dinner I made salmon teriyaki, miso soup, rice, and pickles.
โฆ
I think a trusted piece of software such as your operating system should be in charge of managing permissions. For example, I believe with Wayland on gnome you no longer need to promise you aren't secretly taking screenshots of the whole monitor and shipping it somewhere because to do that Wayland requires you to get user permission.
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.

