msy

This is entirely on brand with the Australian startup scene, absolutely lousy with hangers-on, cosplayers and washed-out bankers & consultants that have never built a thing. There's a lot of seriously talented engineers trying to build real tech but they get drowned out by this kind of rubbish.

I couldn't disagree more. Outside of exotic scenarios where things like formal proofing are possible and economically viable I've never seen a process that prevents bugs, only culture. Good engineering cultures are also often ones with well defined and tested processes and good testing practices but it's the culture and people giving a shit that makes the difference, not the other way around.

Good product cultures are ones where natural communication between the field and engineering would mean issues get reported back up and make their way to the right people. No process will compensate for people not giving a shit.

The point is if the problem is the same in both you need to re-examine the pros and cons. Given the other issues in America and other advantages in China it's no longer a simple equation.

Does anyone know how widely FoundationDB is now being used at Apple? I know they run a huge Cassandra cluster, does this serve a different use case?

Strongly agree, this feels very close to gee-shucks-weren't-things-better-in-the-olden-days regressive history-revisionist trad content.

I don't buy this. Real small business have enough problems that trying to vibe code a Xero replacement isn't really high on the todo list.

You could apply precisely the same cynical calculus to engineering but I suspect a lot of the people nodding along with this could suddenly find it offensive when applied to their mission-critical DevSecOps roadmap.

The reality is there's always work to done responding to changing user needs, market forces and organisational objectives and it's not uncommon that UI design overhauls are driven by an abstract desire to make things seem 'fresh' but that doesn't come (solely) from designers, it's often a top-down strategic directive.

And SBF of FTX fame was ex-Jane St so obviously was a serious finance professional. This is why using past employers as a shorthand for capability is unwise.

'Replace every 15-20 years' is not maintenance. Neither is replacement in the case of catastrophic weather events that'll have you replacing all your windows as well. The only 'maintenance' solar panels benefit from (which is still entirely optional) is occasional cleaning.

Counterpoint: Zelensky.

Kamal has a lot of rough edges (still can’t support custom certs for example) but is still a far more mature solution. It does less but better.

If you genuinely believe the real problem here is reporting, not that it's unclear (and had to be denied by the President himself) whether a private citizen with massive and well documented conflicts of interest and who doesn't hold a TS clearance was briefed on some of the nations most sensitive military planning I'd suggest I'm not the one with an information consumption and evaluation issue.

They’re briefing Elon Musk on China war plans, I don’t think the current leadership will care much where they source weather data as long as it aligns with the current ideological purity purge.

On a related note - how are people tracking the absolute thicket of permissions quirks that is Github's various secrets, tokens & repo permissions?

Agreed. Europe won't be sovereign until it fully controls its social media, having American billionaires (or the Chinese state) able to manipulate the narrative at will is unviable. Look at the recent situation in Romania with Călin Georgescu or Musk's pro-AFD meddling. It makes the pearl-clutching in the UK about the ownership of the Telegraph look hilariously quaint.

You sound like Americans talking about Japanese cars 30 years ago.

It's not just about 'UX backward compatibility', it's the epitome of an expert user interface. If you don't know what you're doing it's near unusable but once you've mastered it the speed at which you can operate is incomparable to 'normal' software. It's also one of the few examples of this outside of software engineering tools.

I mean the price is but the fit and finish is offensively bad for the money vs a BMW/Merc/Lexus/Volvo.

Near term inflation but more broadly increasing paralysis of business investment of all stripes in the fact of a wildly unpredictable political landscape.

Until you get a

  Widget.OtherFlavor = 'Vanilla'

Brits and Europeans died for America's last two wars, on a percentage basis more Dutch and Canadian troops died than Americans. Nearly 500 British troops died for your war.

Next time America asks for assistance, whether it's troops or firefighters I hope the attitude is reflected back and it comes with a costs+ invoice due up front.

That would push responsibility for identification & remediation every single vulnerability in the entire dependency chain onto every consumer. Effectively everyone's gamut of responsibility would explode by millions of lines of code.

Insanity. The US cultural revolution is going to do the same to American scientific progress as it did to the Chinese.

Oddly enough if you access & summarise all the research on vaccines you're going to appear pro-vaccine.

There's an additional issue with timezones I'm surprised he didn't mention - you're off by a day. This means nobody is around on your Monday because it's US Sunday and conversely US Friday is your Saturday morning. This means you either need to adapt to having 4 days a week of overlap, or you need to shift your life to accomodate 7am meetings on a Saturday morning.

There's also regular chaos with the mis-matched DST windows meaning meetings will swing about by 1-2 hours multiple times as the seasons change depending on whose calendar created them, it's manageable but inevitably there's misses and confusion or someone's 8am suddenly becomes a 6am without rescheduling.

The bigger issue however is if you're the AU leg of a global firm with a US plurality: If there are teams in the UK or EU for example there's simply no way of operating with overlap that doesn't involve someone regularly having meetings in the deeply inhospitable early hours of the morning.

Glean are already well established in that space.

The fundamental problem is that in our fully networked era software cannot _not_ be maintained. Security issues are inevitable, cloud/sync/store systems require servers, upstream APIs, libraries & operating systems are constantly shifting and breaking things.

So OSS aside (which has its own complicated economics) someone needs an ongoing revenue stream for that work to happen. Whether it's through regular release of paid upgrades (and EOL of old ones) or a subscription model is these days less of a fundamental separation and more of a question of cadence.

Take a look at the much-vaunted Campfire from once.com - there's been zero new features since initial release and I'll bet the cost of a copy come Feb next year when it's a year old there'll be a 2.0 for another $300. How long after that will 1.0 be EOL'd? So are you really 'buying once' for $300 or paying $300 a year just with the auto-renew turned off?

If you're interested in how this is put together the repo is here: https://github.com/g-trees/g_trees/ and it uses https://github.com/worm-blossom/demo_macromania.

Companies like Radford have been doing this for decades and are used by pretty much everyone, Pave is just a more efficient version of the same game.

You’re accusing someone of ‘extreme hypochondria’ for saying a new vaccine is exciting. That is not a ‘clear question’, it’s a baseless accusation.