fuzzy2

Really now. It's obviously veg.+ns: vegans and vegetarians.

Sure. And how do you pay? I mean, really. You're forced to create an account, then link a payment method (PayPal and/or Visa/Mastercard may or may not be supported, Apple Pay almost never is). Sometimes you also have to link a mobile phone number or the number is the account identifier.

How is that an alternative?

Wow that sounds like the absolute worst. My condolences. In projects I manage I even try not to use containers for the service being developed. (Only for its dependencies.) Everything that affects cycle times must go.

That being said, you should also have a dev environment. QA isn't for development. It'll certainly be cheaper than firing people.

Still a problem irrespective of algorithms used. I recently set up an account on a website, letting my password manager do its thing. Couldn’t log in. Turns out the password was too long (20 chars when 16 were allowed) and was silently truncated during signup.

The login form of course used the entirety of the password, not truncating it. Fun stuff.

Mobile games, especially those with microtransactions. They're highly incentivized to offer a satisfying user interface. So as to get more money, of course.

Sensirion has the SCD40, which appears to be based on the same principle. It's much cheaper than the SCD30.

Oh, user separation is not a security boundary? I was not aware! Let’s all work as root then! /s

The fact that this was the norm on single-user Windows workstations until Windows Vista is astonishing, to say the least. How anyone could want that back is beyond me. It enabled malware to compromise the entirety of the computer with ease. No exploits or anything required! Certainly not one of these pesky UAC prompts!

Can you still shoot yourself in the foot with UAC? Yes. You own the PC. You should be able to shoot yourself in the foot, by willingly deciding to. Not accidentally.

If it has a performance impact, that's not on Windows but the software. Many games are really really badly made software, so that's not surprising.

UAC is the single greatest security improvement Microsoft ever created.

Blocked by Sophos (at work) because “ParkedDomain”. I fucking love this timeline.

Capitalism happened. Experts are profit-oriented now.

Already discussed quite a few times:

https://news.ycombinator.com/item?id=40954535

https://news.ycombinator.com/item?id=40966312

https://news.ycombinator.com/item?id=40952330

https://news.ycombinator.com/item?id=40971247

https://news.ycombinator.com/item?id=40965161

...and probably a few I missed.

I very much dispute the claim that devs are not allowed to think big. It’s just that they take the easy way out. After all, others are taking care of the visual design, requirements engineering, reporting, controlling and whatnot, right?

It’s fine, really. But then please don’t try to overstep the role you assumed.

In my opinion, it is critical you do both: Know the big picture, the vision, build a technological vision based on that. And then you must work on this, in bite-sized pieces. From my experience, in all but the smallest projects, not working iteratively (“experiment”, as you call it) is pretty much a guarantee to build the wrong thing from a user/customer requirement standpoint. Not having the technological vision is also guaranteed to result in a steaming pile of tech debt.

I don’t see a problem with providing reasonably accurate long-time estimates either. Build your technological vision and you’ll know. Everybody knows and will understand that substantial requirement changes or newly discovered requirements will change the timeline.

Though my employer certainly could be categorized as a feature factory (individual software development), we kind of sell the opposite: Sustainable development producing software which can be changed easily. There's only direct monetary compensation. Hierarchies are flat. Like, too flat.

I understand many do not have the energy to fight the status quo and some may not have the… eloquence to do so. I have worked very hard for many years to end up where I am. If others don't, I expect them to at least accept where they remain. Because they don't do "don't care". They are effectively sabotaging projects.

They certainly aren't unintelligent. They still act pretty dumb. Again, I must apologize for my polemics.

The perceived misery you describe I feel is self-inflicted. Many devs "below" me have become entirely disconnected from customer needs, instead only focusing on "interesting" dev problems.

Why do developers only work on ticket-sized portions of the actual requirements? To put it succinctly: because they are simply too dumb. They cannot wrap their heads around it. They cannot grasp it.

Do I sound frustrated? I am. It is inscrutable.

Sorry.

And how do you propose Regular Joe procure a license? Not trying to be snide, but LTSC is an enterprise product that is only available with volume licensing.

So unless you want to pirate it…

I think that's fine, though maybe surprising. Regular PCs don't have redundant power at all and we still update their firmware all the time.

Dunno if you’re aware, but there’s also Fedora’s Atomic Desktop, which is actually more similar to Steam OS, as far as I can tell. Built on top is Universal Blue, which includes an actual Steam OS remix called “Bazzite”.

Conceptually, it is very different from NixOS, with image-based updates and all.

Exactly this. Not only would they not know the tech challenges, they also wouldn’t know the business/domain challenges.

Can WinDirStat deal with hard links nowadays? Windows uses them extensively in the WinSxX folder and possibly elsewhere.

I've opened a few bugs, mostly surrounding extensions. Bugs from the XUL days still exist today, even though the UI is different and the API is different and everything. It is somewhat astonishing. I filed most of them over 10 years ago.

So no, just closing them because they'll be accidentally fixed isn't the correct argument IMHO. Instead, they should just admit that most stuff will never get fixed and just clutters the list. Even though that hurts.

Why blame anyone at all? Did everyone work to the best of their knowledge and beliefs? If not, why? And if they did, how are they to blame?

I make incorrect decisions all the time. I will continue to make them. Because I do not shy from making decisions and neither should anyone else.

Haha, oh yes. Ever had a project where, at some point, the (key) users said “but Excel”? Well, you better listen to them. Sure it may be great for the layperson to edit a building’s layout visually. But know what? The expect just wants to enter the coordinates. In a grid, using only the keyboard.

I’ve had so many projects where we took users for fools. Boy did they fail.

Just curious: Why not use GitLab Community Edition? At least for me, it had everything I wanted. (Due to feature creep, I no longer use it.)

Um, yeah, that's… IMHO exactly where an MVP is supposed to end up. The “VP” says that.

I may not have communicated this well enough. I wasn't referring to a multi-step process where I hand over the solution in between. I was referring to getting good at making in work, right and fast in one step (at least as far as the customer is concerned).

Many try do it all at once and then end up with… nothing.

I don't see how that's a problem. It's not for everyone, yes, but I like it a lot. Talking directly to the customer allows me to create exactly what the customer needs, without any convoluted process.

If that's not for you, you need at least a requirement engineer between you and the customer. That's also okay.

From my experience, getting things done quick is almost never relevant. Getting things done “cheap” is.

I’ve had the opportunity to work with lots of mechanical engineering corps to date, and I can confidently tell you: Even if they had some platonic ideal, they would never be able to follow through. The mediocrity of their software development practices is… profound. On all levels of the hierarchy. Sure they care about the ideal of sustainable software development, but they just can’t do it.

On the other hand, my employer advertises clean code as a service, and this attracts the kind of developers you describe.

Sounds like you might be better suited for working at a company that doesn’t do products but rather projects for others. Plenty of architecting to go around. Any if you get to work on enough new projects, you actually get the chance to make projects succeed faster by iterating on initial architecture and project setup.

It’s still all meaningless bullshit of course, but it’s others’ bullshit.

I think “industry” strongly implies “corporate world”.

However

> The corporate world doesn’t give a shit about finesse, abstractions, witty or beautiful code.

Guess I’m the corporate world then! Listen here, dear colleagues: Before attempting any finesse, abstraction, wit or beauty, maybe first try to make it work to spec. Because otherwise it is entirely worthless.

If you are reasonably good at making it work, you can then make it right and maybe even fast.

Thanks, that's interesting. It allows one to stick to "regular Linux filesystems", which is probably a good thing.