Oh gosh you’re right. I think I was confusing it with how I previously used the list() constructor, which I no longer use. Thanks for the clarification.

This is also necessary for lists in python with one member. Or was.

I believe you just described MCP

And Australia! And I am from both.

I imagine you are right

Feel free to repost

Eat my shorts, honky

True and well articulated.

This is a bigger and bigger red flag as I gain experience.

That, and neglecting the absolutely most important part of the app - data structures and their relationships. Including a deliberate level of normalisation.

Just shoving JSON into Mongo/DynamoDB means that you haven’t thought things through enough.

It doesn’t even make sense to hire a full time architect unless you’re constantly producing new solutions.

You could make an argument that an architect can intervene when existing products aren’t optimal but those skills should be in the domain of whatever senior developer you have lying around

When this job is frustrating, it can be the most frustrating of any type of job.

Sorry and thank god you got out.

Hell yeah living my dream. What would you fire them for? Any patterns?

Being obtuse for a moment, let me just say: build it right!

That means minimalism! No architecture astronauts! No unnecessary abstraction! No premature optimisation!

Lean on opinionated frameworks so as to focus on coding the business rules!

And for the love of all that is holy, have your developers sit next to the people that will be using the software!

All of this will inherently reduce runaway algorithmic complexity, prevent the sort of artisanal work that causes leakiness, and speed up your code.

deleted by creator

Why am I suddenly seeing this guy’s name every single day? Is it a Lemmy thing?

TLC: Taylor, L’Hospital, and a constant

The proper use of getters and setters is not to use them IMO

Saved this comment. No notes.