HN user

globalreset

1,008 karma
Posts2
Comments195
View on HN

I'm surprised about the negativity in the comments. I'm happy someone is testing alternative approache. If they're wrong, they just wasted a bit of their own capital. If they are right - we might all benefit. You've got to treat technology as means to an end, not a religion that requires conformity.

Like `style` or `input`?

People got so stuck on JS for decades that they've forgot that HyperText in HTML is there for a reason. It was always supposed to be more than just UI descriptor markup.

It is JS who is out of place in web. A little script in form of DHTML that grew into becoming a cancer that it is now.

It doesn't matter if we get rid of The Agile. If you make The Agile go away, there will be something else, equally horrible.

The internal incentives in hierarchical organizations is to balloon the management, which suffocates the bottom of the pyramid. That's just how the world works, for most people, not just SWE. The Agile is horrible because corporate management makes everything horrible.

If you don't like it work in a small, carefully selected startup, or make your own company. Otherwise just accept that you're just a corporate drone and you have to endure the shitty corporate system to pay your bills. At least you get paid decently, because there's not that many people to replace you like in other professions.

I disagree. Merge conflicts are just a fact of life, and line-granularity has good usability properties (displaying and editing). `git` has issues, but I don't see merge conflict granularity being an issue, especially when project enforce consistent&automatic formatting.

I agree however that while Pijul is technically very interesting, it doesn't seem to have any killer features that would overcome the cost of switching to a niche version control.

fear of repercussions is mostly gone.

Is it? Because AFAICT people censorship themselves online all the time for the fear of repercussion. It's like being on tape 27/7 where anyone that doesn't like you can watch your old tapes and loook for problems.

Large part of biggest crimes I've seen in software comes down to picking some allegedly good property and optimizing for it irrespective of costs and limitations it involves. Encapsulation, modularity, flexibility, readability, purity, testability - you name it. Some dubious, some reasonable - no matter what, it usually involves costs and drawbacks.

I have 99 big problems developing software, and not being able to read it from start to end ain't one.

I'm a bit jealous for people advocating such things, being able to work on software tiny enough to even be able to think this is practical. Literate programming could work for tiny software that can be approximately flattened to a 1d "story": "beginning -> end" with only minor detours.

Most of projects I worked with was large enough that things are optimized precisely for not having to understand large parts that were abstracted away (and the problem is to try to do it without introducing too much complexity).

Love both Tailscale and Xe's writing as well, and indeed, all these (rather irrelevant) images are just breaking the flow of reading/skimming the content. I guess I'll just watch the video instead.

Manager are for managing low skilled workers that need supervision and help. The idea that you hire "the best SWEs" and then you have to slap a manager to oversee them like they are burger flippers is ridiculous on its face.

SWEs might benefit from some help from experienced technical leadership - someone to consult, get feedback from etc. and from bureaucratic assistance (help get paperwork out of the way), but typically "SWE manager" position is akin to fast-food chain manager in a SWE shop.

Sending people with guns just because someone shared sequences of words you claim "ownership" over is a cost and harm. Society does not inherently owe you keeping your ideas exclusively controlled by you. It's a form of a artificial, but pragmatic concession in the hopes it will encourage people to produce more interesting sequences of words. If it wasn't for social consensus you would not be able to control it and wouldn't be able to do anything about it (unlike physical property, which you can physically protect).

Billions of people all over the world go about their lives just fine, worrying about mundane things and slowly improving their situation every day. Almost all objective metrics point out at the human population doing better than ever and life being as best as it ever was.

Someone somewhere said "the end is near", so let's ignore all the counter-arguments and counter-examples, human ingenuity and technological capability and weep instead.

Inserting batches of items in one db transaction is faster in Posgres as well, in my experience. I expect that to be the case for all rdbms. Each transaction has a cost of "flushing", and every non-transaction query is implicitly a transaction. By doing multiple operations in one explicit transaction, the overhead of a transaction is amortized over more operations.

Isn't that expected and natural?

As performance of a system is being optimized, the relative size of un-optimizable parts goes up.

Sure, your banking app crashes sometimes and annoys you. How about you delete it and instead take a bus to a postal office to pay your bills this way - no annoying apps involved, it will just take 1h instead of 1m.

That `run=true` was just bad API: "boolean trap", yada, yada. The rest of "80% abstraction" idea is not well supported, and I don't buy it.

The abstraction is either good or it isn't. Some stuff just does not abstract well. A function or an API is not necessarily "an abstraction".

I would not extrapolate from a single case. Language makes some minor tweaks, etc. someone gets unlucky and keeps hitting issues in their own codebase and their dependencies, so get rightfully pissed.

Even in allegedly super-stable and backward compatible languages, in a large enough codebase you'll keep hitting issues when you change deps/compiler versions. If I could get $1 every time a C++ package refuses to compile due to some weird compilation issue...