abhibeckert

Sure - but in the real world that mostly only happens when the documentation is an afterthought.

Here's a tip on good documentation: try to write the documentation first. Use it as your planning process, to spec out exactly what you're going to build. Show the code to people (on GitHub or on a mailing list or on lemmy or whatever), get feedback, change the documentation to clarify any misunderstandings and/or add any good ideas people suggest.

Only after the docs are in a good state, then start writing the code.

And any time you (or someone else) finds the documentation doesn't match the code you wrote... that should usually be treated as a bug in the code. Don't change the documentation, change the code to make them line up.

Have they released who is going to pay for these power plants? Because if they put it on my monthly bill, I’m going off grid and I bet half the rest of the country will too.

Sure we can make a different ticket for that to move this along, but we’re getting product to agree first.

Ooof, I'm glad I never worked there.

QA's job should be to make sure the bugs are known/documented/prioritised. It should never be a roadblock that interrupts work while several departments argue over what to do with a ticket.

Seriously who cares if the current ticket is left open with a "still need to do XYZ" or it gets closed and a new one is open "need to do XYZ". Both are perfectly valid, do whichever one you think is appropriate and don't waste anyone's time discussing it.

Um... the headline seems to be completely backwards.

Surely the councils that can't meet the target should get extra funding so they can meet the target?! From the the content of the article, that seems to be what is actually happening.

Unique password of course.

Passwords didn't leak - so that's not helping you in this case.

What name/email/phone/credit card/home address/etc did you give them? Because that's what leaked.

If any of that is part of the hiring process - I don’t want the job.

If HR is incompetent enough to consider things like relationship status or political opinions then what other bullshit policies does the company have? It’s probably the tip of the iceberg.

By far most important thing is to have good colleagues, because without good colleagues your job will be miserable or the company will not last (or both). Made the mistake of working for a shitty job at high pay once and it was one of the worst decisions of my life.

Don’t waste your life working for incompetent companies.

Also, as someone who has hired devs... if you have a public profile, and it doesn't make you look hopelessly incompetent, then your application is going onto my shortlist. Too many applications cross my desk to look at all of them properly, so a lot of good candidates won't even get considered. But if there's a GitHub or similar profile, I'm going to open it, and if I see green squares... you've got my attention.

You'll get my attention wether the username matches your real name or not, but bonus points if it's your real name. Openness leads to trust. And trust is criitcal.

Bus beats the pants off light rail in just about every respect you can think of

Um, no. The only reason I would ever set foot on a bus is if there was no rail option.

It’s quickly scalable up and down

It really isn't.

it can be rerouted on a whim

I was on a bus that was rerouted once - when a road closed unexpectedly. We were 10 minutes drive from home, and the new route took us 20 minutes in the opposite direction, we waited 30 minutes for a bus that could drop us off 45 minutes walk from home. Including the original bus trip it was about three hours and by the time we got home we were dangerously dehydrated (we had water with us, but not three hours worth).

The ability to reroute buses is not a positive attribute. It sucks.

it doesn’t require additional road or electrical infrastructure to operate

Yeah it does. You need bus stops. Bus lanes. And these days you need totally do need electrical infrastructure — according to my city, the total cost to the tax payer for diesel vs electric works out to $70,000 per bus if it's electric... and that includes spending a fortune on electrical infrastructure upgrades to be able to charge those huge batteries. Batteries a train doesn't need because they would never go hours between charging the train.

Spare parts are plentiful and the parts economy is competitive, maintenance overheads are lower, the fleet is amenable to reuse in non-PT contexts, etc.

I don't really see how busses are that different from trains. Pretty much the only difference is metal wheels vs rubber wheels. I would think the metal ones last longer.

Ultimately, a bus is always slower than driving. Light rail, on the other hand, is often faster than driving.

Yeah I've given up on integration tests.

We have a just do "smoke testing" — essentially a documented list of steps that a human follows after every major deployment. And we have various monitoring tools that do a reasonably good job detecting and reporting problems (for example, calculating how much money to charge a customer is calculated twice by separate systems, and if they disagree... an alert is triggered and a human will investigate. And if sales are lower than expected, that will be investigated too).

Having said that, you can drastically reduce the bug surface area and reduce how often you need to do smoke tests by moving as much as possible out of the user interface layer into a functional layer that closely matches the user interface. For example if a credit card is going to be charged, the user interface is just "invoice number, amount, card detail fields, submit, cancel". And all the submit button does is read every field (including invoice number/amount) and send it to an API endpoint.

From there all of the possible code paths are covered by unit tests. And unit tests work really well if your code follows industry best practices (avoid side effects, have a good dependency injection system, etc).

I generally don't bother with smoke testing if nothing that remotely affects the UX has changed... and I keep the UX as a separate project so I can be confident the UX hasn't changed. That code might go a year without a single code commit even on a project with a full time team of developers. Users also appreciate it when you don't force them to learn how their app works every few months.

I’d vote for a ubi in a heartbeat

With you there.

and lower home prices.

The issue is just not that simple to fix.

ChatGPT 4 was a little reluctant and asked for more details... when I refused to give any I got:

Apple Music is very good (and you don't need an iPhone). For me at least it recommends good songs, but even better you don't need to use those. There are extensive playlists that are manually curated by experts - for example Aussie Pub Rock is a hundred song playlist that is regularly updated by their team of editors.

Audio quality also tends to be better on Apple Music. They encourage recording studios to produce a "Mastered for iTunes" mix and have strict quality controls as well as training for the recording studio to make sure they do a good job. You won't find anything amateur with that label but even for professional massive artists I think they sound better there too - because Mastered for iTunes tracks are intended to be listened to with relatively neutral speakers/headphones (the only kind Apple sells) while a lot of other services have professionally mixed sound tracks designed for bass heavy speakers that so many people have nowadays out side of Apple's walled garden. I find I often need to boost the base to get good sound from Spotify/YouTube Music/etc because they assume your speakers will do that for you.

The difference isn't subtle - I'm not talking about a 256 vs 320 Kbps encoding difference. The same song from a major artist (e.g. Taylor Swift) will often sound totally different on Apple Music. Wether it sounds "better" depends on your speakers, but with my speakers (which are not from Apple), they do sound better. A lot better.

But personally I've gone back to just buying music. The idea that I'll pay who knows what ever month for the rest of my life... no thanks.

I'll jump on YouTube occasionally to discover new music, but i'm not paying for it (Apple Music, sadly, has no free tier... but it does have a free trial).