>> Apple has offered products with little value over competitors

My Pixel dropped connections unexpectedly. The battery would barely last till end of day.

Apple hardware is simply better value for the money

maybe writing code is cheap . But writing unit tests that actually test stuff that matters is suddenly so much more important and expensive.

Yeah it's more important, but I think that has become a whole lot cheaper too.

Humans are accountable to each other. Humans can be shamed in a code review and reprimanded and threatened with consequences for sloppy work. Most, humans once reprimanded , will not make the same kind of mistake twice.

> Humans can be shamed in a code review and reprimanded and threatened with consequences for sloppy work.

I had to not merely threaten to involve the Ombudsman, but actually involve the Ombudsman.

That was after I had already escalated several times and gotten as far as raising it with the Data Protection Officer of their parent company.

> Most, humans once reprimanded , will not make the same kind of mistake twice.

To quote myself:

  other people in their own team had already admitted this, apologised to me, promised they'd fixed it, while actually still continuing to send letters to the same non-existent address.

I used to be a big advocate for Salesforce in my organization. And it was really great .. allowing us to deliver new functionality without the usual IT procurement bureaucracy.

Now with cloud maturity and Vibe coders who will get better and cheaper, I think it's possible to replace all the features we use on Salesforce at a fraction of the cost of our Salesforce licensing cost.

counterpoint: why would sales people want to use a different crm each time they job hop every 2-3 years?

FoundationDB Record layer doesn't get much attention here but I have found that all my use cases are satisfied by it.

And I get the benefit of resiliency and DR for free.

If you are a developing for My SQL and you are using Java/kotlin/closure/scala consider this as well.

If I may ask, does the code produced by LLM follow best practices or patterns? What mental model do you use to understand or comprehend your codebase?

Please know that I am asking as I am curious and do not intend to be disrespectful.

And what’s the name of the company? I’m fixing to harvest some bug bounties.

Think of the LLM as a slightly lossy compression algorithm fed by various pattern classifiers that weight and bin inputs and outputs.

The user of the LLM provides a new input, which might or might not closely match the existing smudged together inputs to produce an output that's in the same general pattern as the outputs which would be expected among the training dataset.

We aren't anywhere near general intelligence yet.

Ignoring your last line, which is poorly defined, this view contradicts observable reality. It can’t explain an LLM’s ability to diagnose bugs in code it hasn’t seen before, exhibit a functional understanding of code it hasn’t seen before, explain what it’s seeing and doing to a human user, etc.

Functionally, on many suitably scoped tasks in areas like coding and mathematics, LLMs are already superintelligent relative to most humans - which may be part of why you’re having difficulty recognizing that.

I get your sentiment but a lot of people on this forum forget that a lot of us are just working for the paycheck - I don't owe my company anything.

Do I know the code base like the back of my hand? Nope. Can I confidently talk to how certain functions work? Not a chance.

Can I deploy what the business wants? Yep. Can I throw error logs into LLMs and work out the cause of issues? Mostly.

I get some of you may want to go above and beyond for your company and truly create something beautiful but then guess what - That codebase is theirs. They aren't your family. Get paid and move on

Do you work as a consultant then? I've been with the same employer for a long time, so if my team creates a mess, I get to look at it daily.

Spring AI is fantastic for Java shops. I am assuming Typescript devs will enjoy Mastra just as much .

Gemini's large context window is incredible. I concatenate the my entire repo and repos of supporting libraries and then ask it questions.

My last use case was like this : I had a old codebase code that was using bakbone.js for ui with jquery and a bunch of old js with little documentation to generat UI for a clojure web application.

Gemini was able to unravel this hairball of code and guiding me step by step to htmx. I am not using AI studio; I am using Gemini subscription.

Since I manually patch the code, its like pair programming with an incredibly patient and smart programmer.

For the record, I am too old for vibe coding .. I like to maintain total control over my code and all the abstractions and logic.

I had Gemini ingest our huge aws cloudformation repo . I had it describe each infrastructure component and how it related to others and creation hierarchy and IAM.

I got a nice and comprehensive infrastructure requirement document out of this.

Now I am using it to create Terraform repo , deploying it via OpenTofu and comparing it to my existing AWS cloud formation . This part is still a WIP .

Yes the cost of building software dropped by 90%.

However, the cost of software maintenance went up by 1000% . Lets hope you don't need to ever add a new business rule or user interface to your vibe coded software.