1,307 karma · joined August 9, 2013
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...
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.
> 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.
That's a great quote.
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
Nice idea, but it needs a LOT of TLC to make it generally useful. I suspect that having a non-numeric "zip" code and a non-US address might be breaking a lot of the automation.> 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"?
> 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]
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.
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.
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.
> 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.
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.
[0]: https://en.wikipedia.org/wiki/Live_%3F!*%40_Like_a_Suicide
As of March 2026, OpenAI generates annual revenue exceeding $12 billion. However, the costs of running ChatGPT are around $17 billion a year.
Source: https://searchlab.nl/en/statistics/chatgpt-statistics-2026
We're minting an entire generation of people completely dependent on VC funding. What happens if/when the AI companies fail to find a path to profitability and the VC funding dries up?
Strong disagree. Coding was the fun part. Reviewing PRs is not.
1. In the Dundas/College triangle, there are are 2 stops less than 100m apart. 2. At the Queen St turnaround, there are 4 stops all within 150m of each other 3. At Bloor St, there are 2 stops 100m apart
These are all within a single 2km section of the bus's 10km route.
This time would be much better spent watching these 9h of lectures.
This sums up many things perfectly. I'll be stealing this.
Open mic nights at your local bar are a great source of data. Approach people after their performance, compliment them, and ask them if they have a coach they'd be willing recommend.