intelVISA

Some Saturday morning cartoon villain behavior, lol.

Well it's not UK specicfic but as there's only really workers and owners, they could be insecure about being a slightly better paid worker?

Most apps are trivial for a decent dev to reproduce, I'd wager the root problem is rarely the codebase: the org is rotting. Years of 'fixes' with no progress is like blaming the water for sinking a ship.

Success attracts deadweight who (un)intentionally sandbag efforts to reverse this downward trend for their own self-preservation. I don't blame them, doubt there's a fix when the system requires most people work bullshit jobs instead of collecting UBI.

Comms is a Hard Problem, but specs should not be regularly ambiguous that they require daily course correct - huge velocity killer.

seems like it

One imagines the same reasons you would learn Unix and DSA even if your job is writing GET handlers and wrestling Python venvs. Gives you some base system-level context even if rarely immediately useful.

Sounds great, much better than rote drugery imo!

The dental 'Rewrite it in Rust' gambit?

IOMMU is my borrow checker

Good lord, are all those non-tech managers the reason Europe can't seem to build viable tech companies?

Why pay when better code's free?

Plus KVM is GPL right? That means more open source code (albeit spaghetti, given the origin)

> can't be copyrighted because they're considered functional instructions

by that logic software shouldn't be copyrighted either!

You can also discern some flickering lights in your periphery that are otherwise 'solid' when focused on. Quite annoying.

Hopefully it's not a result of the cerebral plastics..?

2 out of 3 of those maxims are Reasonably Correct?

Soon(tm)

Why is best inferred from context imo, otherwise it's a smell for a system with too much scope.

Anyone pushing packets seriously doesn't even use syscalls...

Good code is fairly self-documenting, but alas.

You would dare refuse the offer of doing the heavy lifting while he 'manages'?

How horrifying!

Really nice, can't believe any good place would turn this down. You should be relieved, in a way.

;)

Yep, software is about cohesion. Having one side beloved by product and blessed with 'the offense' racing ahead to create extra work for the other is not the play.

Even when they rotate - who wants to clock in to wade through a fresh swamp they've never seen? Don't make the swamp: if you're moving too slow shipping things without sinking half the ship each PR then raise your budget to better engineers - they exist.

This premise is like advocating for tech debt loan sharks; I really hope TFA was ironic. Sure, it makes sense from a business perspective as a last gasp to sneakily sell off your failed company but you would never blog "hey here at LLM-4-YOU, Inc. we're sinking".

Please don't soapbox under false pretenses - in no world does this "200mb non-shared dependency" comparison exist: that would imply static linkage is just appending a shared object into the executable at compile-time.

Indeed, I'm biased but often the arguments in favor of shared objs have fundamental misconceptions that betray a lack of lower-level tinkering that makes it hard to take seriously.

I get where they're coming from as excellence does require grinding - the idea of a 3 week bootcamp into mastery (of anything) is a pure sales pitch; on the flip side the grind's a means to an end, usually, and I am doubtful that goal is "become indentured to a company" when they've just built up the skills to found one.

> Does "working class" have a different meaning today? When I entered the job market it meant "blue collar" or manual labourer. You seem to be indicating that you're what used to be called "knowledge worker"?

If you stopped "working" tomorrow and had no means to generate income e.g. from ownership of capital you're working class.

So if you make bread, car wheels or SaaS for a living it doesn't matter, only whether you own the output and can sell it. Social class is a distraction from this economic reality.

I think this comment should be framed as a solid example of why you shouldn't have non-tech people manage tech teams. Feudal mindset that doesn't represent development outside of bottom tier tech companies.

Then again... engineers like to think themselves Super Smart(tm) yet forget who's paid to do all the fun sidequests while ya'll stuck "chopping onions" for those 'dumb' Product Lords.

> Engineering was responsible for the implementation, the design, the product-market fit, the customer need, everything.

I generally agree but it's a tough sell hiring talented people as effectively one man startups with no equity.

Plus, without UBI it's not fair to remove so much organizational padding: getting paid to decorate JIRA boards may not bring any value but it keeps someone's family fed.