home-baked

Some of them can be as simple as using a hashmap instead of some home-baked data structure.

Same if they let a framework handle the switch instead of a home-baked solution.

I would never have had my business sign-up for it and I would continue with home-baked solutions for disaster recovery.

There are enough scientists that say the distinction is often hypocritical (example from an article: a factory-made carrot cake is labeled UPF, but a home-baked one isn't, even though they're practically the same thing).

I'm not sure if they're using Scalagen under the hood or their own home-baked stuff.

>a factory-made carrot cake is labeled UPF, but a home-baked one isn't, even though they're practically the same thing).

You can then monitor progress, have robust cluser-wide error handling, and your data gets nicely merged into output files in S3 (not so easy with the home-baked solution).

And I bet that they'll reverse that moronic decision eventually once ApplePay gets sufficient traction and cuts into their bottom line, and/or their own home-baked store-specific solution doesn't take off.

By Liskov substitution principle, or with the set view of types, subclasses are always specializations / subsets, unless you're introducing some kind of home-baked type system built on top of the existing type system.

Ideally the home-baked software that I build will be just using very simple technologies, and I can just vibe/LLM code all the dependencies, or worst case just vendor it, and update it once a year or longer.

That looks neat -- I've been using a somewhat similar little home-baked thing of my own (simple shell script wrapping gpg), largely because I wanted a simple command-line password manager and this 'pass' thing I've been seeing linked in various places strikes me as (a) pretty poorly designed and (b) quite over-sold -- e.g.