As kids find alternative platforms, perhaps they will be vendor locked to them instead of the Meta empire.

https://en.wikipedia.org/wiki/Complete_graph

At the beginning of a project, the government could spend above market for a great architect to lay down the data model and put some patterns in place which could then be reasonably well maintained by below market rate staff, but there are rules and public pressure.

Interestingly, my local govt hired Deloitte to put in a serverless AWS-based application that could have been a simple CRUD app hosted on a medium EC2 instance. It cost $1.5 million and didn’t work, in addition to the hundreds of thousands per year in cloud costs.

Could have been a Django app with Celery. The cost could have been in the low thousands per year.

It could even have been done with a succinct AWS serverless system.

But that’s not the schmooze that can impress high level stakeholders, themselves less familiar with good design patterns, and win the contract.

“What a person knowingly exposes to the public, even in his own home or office, is not a subject of Fourth Amendment protection. But what he seeks to preserve as private, even in an area accessible to the public, may be constitutionally protected.”

This “lack of privacy in public” absolutism would mean that there would never be certiorari granted for these types of cases in the first place.

Reductionist at best, IMO

See also United States v Jones, Carpenter v United States

https://en.m.wikipedia.org/wiki/Simpson's_paradox

You might choose to add comments and let the logic unfold in a less succinct way in order to improve readability and understandability.

You might also consider your colleagues’ limited cognitive reserves, some of which could be spent on more important issues.

1. The risk of a bad hire is great, and this de-risks that

2. It facilitates more natural and spontaneous conversations, which for better or worse short-circuits a well crafted and pre-planned anti-bias interview process which can be too rigid for both parties to explore detail

I was surprised to find an anti-framework, anti-layering perspective here. The author makes good points: it’s costly to learn a framework, costly to break out of its established patterns, and costly when we tightly couple to a framework’s internals.

But the opposite is also true. Learning a framework may help speed up development overall, with developers leaning on previous work. Well designed frameworks make things easy to migrate, if they are expressive enough and well abstracted. Frameworks prevent bad and non-idiomatic design choices and make things clear to any new coder who is familiar with the framework. They prevent a lot of glue, bad abstractions, cleverness, and non-performant code.

Layering has an indirection cost which did not appeal to me at all as a less experienced developer, but I’ve learnt to appreciate a little layering because it helps make predictable where to look to find the source of a bug. I find it saves time because the system has predictable places for business logic, serialisation, data models, etc.

Also, you can pick and choose what to use in Django similarly to Flask - it just has a higher initial learning curve.

Once you get to sufficient levels of complicated, leaning on established, documented, community supported design patterns and abstractions helps vs. sorting out your imports, making bespoke design choices, and doing a bunch of non-core value producing work.

Only thing I’ve read by Voltaire but it slapped.

The developer that implemented them could have used a few bools but decided to cram it all into one byte using bitwise operators because they were trying to seem smart/clever.

This was a web app, not a microcontroller or some other tightly constrained environment.

One should not have to worry about solar flares! Heh.

Honestly the best UI I’ve seen is the terminal-based one at libraries in the 80’s and 90’s that allowed you to find books. Lightning fast and allowed the user to become an expert quickly, especially because the UI essentially never changed.

If you design things with Occam’s razor in mind, a full page reload doesn’t feel like one.

Nowadays I build software to last as long as possible without future investment of time and effort spent on maintenance. Meanwhile the industry seems to have developed some need to mess with their programs all the time. It’s almost like a tic.

With this in mind, are we underestimating the devastation awaiting the younger generations?

We have scientists cocksure of natural disasters in the medium term, four decades of increasing economic inequality, cost of living pressure, and in the U.S., and increasingly in other countries, price increases in health, rent, and education.

The kids see empirical evidence of their plight.

I also wish that Django would provide native scaffolding a la Laravel and Rails.