pards

Same, but with GitLab pages.

Every hotel I've stayed at in Hawaii charges one - usually to the tune of $50+/day - even if the hotel has no resort-like facilities. It's a bullshit fee.

a light grey text on a white background

This makes the page SO hard to read. Why are "designers" still doing this? Have they no respect for their readers?

Maybe add a dedicated clear button.

It's tedious to have to hit DEL 6 or 7 times towards the end of the game. Maybe ESC could clear the whole word?

This.

100%. It deserves more detail, too.

I've spent many hours explaining how idempotency is supposed to work, and why it's important. Most teams understand the need for it, but very few thought about it up front.

I’ve been finding most restaurant dishes “low quality”

Many restaurants use pre-made components like sauces bought from restaurant wholesalers which explains a lot of the sameness across establishments.

Hollandaise from a bag? No thanks.

> But when 6 people simultaneously tried to pay their share of the bill, chaos ensued.

Hasn't that been a fact of life ?

I remember having to split bar tabs at the end of the night before phones. No calculators. Drunk people trying to do math is a spectacle to behold. Everyone throwing random cash amounts in the centre of the table, taking their own change, and one person attempting to reconcile the total then asking for more contributions if we were short.

Electronic bill-splitting is superior in just about every way.

“We think that all of the platforms, including Meta, need to do more to protect their customers … from the dangers that are on their sites,” she says.

If the service is free, you're the product not the customer

Ref: https://youtu.be/yujF8AumiQo

We recently had an issue with our production Oracle database. Our in-house DBAs spent hours trying to get the AI support bot to assign a real person to join the incident call. It took more than 2 hours to get an actual person on the call.

We literally pay hundreds of thousands a year in Oracle support contracts, and this is what we get? AI bots? Nope. Migrating to Postgres is now a top priority.

This "replace people with AI" nonsense has to stop. [0]

[0] https://www.forbes.com/sites/jonmarkman/2026/04/06/oracles-m...

When AWS first introduced a viable cloud to the world, it was amazing. Back in the 1990s when you wanted to implement an enterprise software solution, you first had to take a guess at what computing power you would need. Next, you would have to order hardware from companies like Sun Microsystems or Dell and that could take weeks if not months to be delivered. It would then need to be racked, powered and provisioned, and then you were screwed if you happened to undersize it or criticized if you spent too much and oversized it.

This is how many large enterprises still operate today. Ironically, the main argument is that it's faster to provision VMs on-prem than it is to get approval to run in the cloud.

Bureaucracy always beats tech.

I was unable to put clients on both Evidence and Prefect because the former failed to attend a sales meeting booked through their website and the latter failed to book a meeting after the ex-real estate agent they hired failed to actually schedule a meeting following outreach also through their website.

the people I tried in Melbourne don’t check their sales inbox.

because the firms I initially tried also don’t respond to their sales inbox.

I cannot state this clearly enough – the bar is so low that it is hard to give people money.

It's amazing how frequently I encounter this phenomenon. I do the homework, choose a provider based on my research, reach out to the provider, and ... crickets.

Automation takes a lot of manual labour

That's a great quote.

https://xkcd.com/1205/

I tried this (as a Canadian):

     1. It asks you to optionally sign up for a bunch of other services like Spokeo
     2. It asks for access to your email via Apple's Mail app which I don't use
     3. I got a lot of 404s anyway
     4. Many sites require manual intervention to work

He argues that it's important to acknowledge that imperfection and work toward processes that improve results.

One way to do that is to automate the prompting process in a way that makes it more repeatable. "When you do that, you identify where you're starting to get good results and you don't expect everybody to come up with a well-structured long prompt."

Wait. Where's the explanation on how to "automate the prompting process"?

For the non-US readers:

COBRA is the Consolidated Omnibus Budget Reconciliation Act. It gives workers and their families who lose their health benefits the right to choose to continue group health benefits provided by their group health plan for limited periods of time under certain circumstances such as voluntary or involuntary job loss, reduction in the hours worked, transition between jobs, death, divorce, and other life events. [0]

[0] https://www.dol.gov/general/topic/health-plans/cobra

This design is perfect irony. I love it.

It's scary. Our society is not set up to deal with mass unemployment.

Nope. Banking.

It's an investment that is not generating returns. It's inventory sitting on the shelf requiring ongoing maintenance costs but generating no income.

Yep, it's 100% a theory of constraints issue. Any optimization not done at the bottleneck (post-development) only serves to worsen the bottleneck.

In my large enterprise world, AI adoption hasn't made it outside of the development teams - only developers have access to Github Copilot.

Code takes 6-12 months to make it from commit to production. Development speed was never the bottleneck; it's all the other processes that take time: infra provisioning, testing, sign-offs, change management, deployment scheduling etc.

AI makes these post-development bottlenecks worse. Changes are now piling up at the door waiting to get on a release train.

Large enterprises need to learn how to ship software faster if they want to lock in ROI on their token spend. Unshipped code is a liability, not an asset.

The moving background detracts and distracts from the content making it hard to focus.

using TDD [...] without focusing on your core product

This. Even in large enterprises, I've seen projects prioritize code metrics over product metrics. A beautiful codebase that nobody uses is completely wasted effort.

In my experience, the level of test coverage has little to no correlation to the quality and readability of the codebase.

These are subjective, of course, but some of the easiest codebases to understand had low test coverage, and some of the most complex codebases had high test coverage. The opposite has also been true.

For clarity, PEBKAC is "problem exists between keyboard and chair"

A few quotes that resonated with me:

it (TDD) makes you feel like a good programmer even if none of it necessarily contributes to the results your team is supposed to achieve.

It also, in my experience, often makes refactoring difficult because the implementation is set in stone, not the behaviour. I know the TDDers say this is because the tests are bad but, like agile, very few people seem to be able to "do it right".

All of the really hard problems are not solved by TDD.

I've never seen TDD iterate towards good architecture. It optimizes for testable logic.

A coding agent permits one to feel as if they have the raw productive power a great programmer can tap into. [...] Those cathedrals are not the great works they appear to be. The construction is shoddy and the architecture nonsensical

In other words, AI allows junior/mediocre devs to _feel_ experienced and produce naive implementations much faster, burying the experienced devs in the drudgery of code reviews and defect triage.

Missing the /s? Most people have a calculator in their pocket all the time now.

I remember having to split bar tabs by hand at the end of the night without a calculator. The waiter delivers a hand-written bill, and we'd calculate how much each person owed, splitting drinks individually and food equally, recalculating tax and tip to derive each person's total. We'd pool the cash in the middle of the table (with people taking their own change as they go where possible), then counting all the cash and making sure it still included sufficient tip. All after many pints. I do NOT miss those days.

Guns N' Roses blazed this trail in 1986 with their faux live EP titled Live ?!@ Like a Suicide [0] which was reissued as the B-side to G N' R Lies in 1988.

[0] https://en.wikipedia.org/wiki/Live_%3F!*%40_Like_a_Suicide