srvaroa

Joined 14 years ago

Karma
359
Submissions
59
Member since
Feb 4
Software engineer, https://varoa.net for long form content. also at https://bsky.app/profile/varoa.net, less so at https://twitter.com/srvaroa
View on Hacker News

Recent submissions

Comment · 6 months ago
This feature is 10 years late
Comment · 1 year ago
Looking forward to someone writing the Spring equivalent this on the JVM
Comment · 1 year ago
I'm sure many people have equated "typing code faster" with velocity, productivity, and execution speed. But I am not doing it.

I'm saying that given N developers, if they all type code faster, you get more code. From the linked text: "Will this translate into a net increase of actual value or just an accumulation of slop and technical debt? Regardless of the answer, there will be more raw code."

The argument I'm making is based on more volume of code. Not on quality, value, etc. of whatever that code is doing.

On your point about nobody having thought "my problem is that can't type fast enough". The problem "shit, I'd know what I want, I'd rather spend 10 minutes typing than 1 hour" is real. An LLM allows you to say "I want a piece of code that does X" and it hydrates that into the 500 lines of code. You materialize the thing faster.

Now. Yes we can go back to your point. Was that idea good? Is the code good enough? etc. Those are valid questions, but orthogonal to my point. My point is not about the quality of outputs etc. It's about "this thing helps you churn more code, and throw it to the systems that digest code".

Comment · 1 year ago
Thanks!
Comment · 1 year ago
Comment · 1 year ago
Comment · 1 year ago
>7. This incident has reminded that many people mistakenly assume that git tags are immutable, especially if they are in semver format. Although it's rare for such tags to be changed, they are not immutable by design

IME, this will be more "learned" than "reminded". Many many people set up pipelines to build artefacts based on tags (e.g. a common practise being "on tag with some pattern, then build artefact:$tag") and are just surprised if you call out the flaws.

It's one of many practises adopted because everyone does it but without basic awareness of the tradeoffs. Semver is another similar case of inherited practise, where surprisingly many people seem to believe that labelling software with a particular string magically translates into hard guarantees about its behaviour.

Comment · 1 year ago
Well, this AI operates now at staff+ level
Comment · 1 year ago
The primary reason I keep writing is that this, the plain written word, is The Platform to transport ideas in time and space. It has passed the test of time in ways that each of those platforms you mention have not (nor any other medium, e.g. video, etc. at least in our lifetimes).

I think of those platforms more as distribution / syndication mediums, using them for stuff like throwing it out there and reach others (which I somewhat care about because the topics I write about are those I like to exchange opinions about with others, but not obsess in terms of needing validation) and keep some degree of isolation from their policies, relative importance vs others, algorithms, UI/UX choices etc.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton