aev_software

I let mine find example code of how some feature should be used. And it’s really sad how often they make something up out of thin air, and how little regret they show for wasting my time.

That’s where I am, too. I let mine find example code of how some feature should be used. And it’s really sad how often they make something up out of thin air, and how little regret they show for wasting my time.

Convenience over freedom / privacy / security / equality / justice. We see this all over the place. Many people prefer comfort over challenge. That seems a survival instinct. And it works against us.

A clear indication of bad requirements.

So what’s your opinion on languages like haskell and erlang, that infer static types?

Once upon a time I worked with a CMS that allowed an admin to delete the CMS itself and also any web server that ran it. Poof: gone. Fun times.

ELI5?

Author wrote a lot of words about data and state, but I’m not sure I understand the argument. Please explain like I’m 5?

I guess it’s possible I’ve been doing OOP wrong for the past 30 years, knowing someone like you has experienced code bases that uphold that promise.

The main lie about these principles is that they would lead to less maintenance work.

But go ahead and change your database model. Add a field. Then add support for it to your program’s code base. Let’s see how many parts you need to change of your well-architected enterprise-grade software solution.

In my experience, when applying functional programming to a language like java, one winds up creating more interfaces and their necessary boilerplate - not less.

Yes, but that’s a really bad situation from a security perspective. ideally you want two separate accounts: the admin who can do everything, and the daily driver whose activities cannot harm the system.

OK but it also imports half the world’s code base in NPM packages alone.

Wait… you asked your AI to create a git branch instead of creating the git branch?

Why?

Try a rubber duck next time. Also, diagrams. Save a forest.

I love documentation if it’s written well and if it’s helpful.

I can’t say I find vim’s documentation meeting either of those criteria.

So I reach out to other sources who figured things out and regurgitate their experiences in ways that fit how my brain likes to consume them.

My app went from a single code base that handles a million different actions to a million code bases that each handle a single action, but they still all depend on each other and still are tightly coupled, but now they’re spread out across 50 disparate cloud services so maintenance effort only got worse.

6 Whole Days!

Try 25 years. And it still surprises me.