1,261 karma · joined April 11, 2017
I am surprised on the lack of creativity when doing these projects. Why don't they start 5 small projects building the same thing and let them work for a year. At the end of the year you cancel one of the projects, increasing the funding in the other four. You can do that every year based on the results. It may look like a waste but it will significantly increase your chances of succeeding.
But we should keep trying to give more opportunities to the less fortunate. Better education, remedial classes, free school lunches, child credits, etc. We do that by asking the wealthy to contribute more. Not by taking away their advantages.(e.g. Admission tests)
My naive take is that there is a need for each. remedial helps kids to catch up. Normal is where you have perhaps 70% of the students, advanced where you have kids with more natural ambition in some subjects and gifted is where you send the top 5%?
I think what I am remembering is this story from Joel Spolsky. Good read. https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev...
https://www.cnn.com/2022/04/19/opinions/masculinity-toxic-me...
We may agree or disagree with Galloway, but we need to pay attention to this issue.
The most frequent problem that I see is that people design Microservices that are "small as possible" instead of "Small enough than a small team can own them". For example, I have seen teams of 5-7 developers owning 20 microservices which is crazy IMHO. I blame the pre-fix micro which is highly miss leading. Now, if you merge together these 20 tiny microservices doesn't make monolith. A monolith would be a service or application that is owned by multiple/many teams.
The other important aspect is that microservices should be loosely coupled and what I see is highly coupled microservices. How do you know you have highly coupled microservices? I have seen a few things.
- They share business logic and developers end up creating libraries with business logic which is very problematic.
- They share access to the tables.
- Changes in one often require changes in other microservices.
- Integration and unit tests are not enough. You need E2E tests, but these are hard to write and brittle.
Even if it doesn't solve the problem for all, it solves the problem for many. Which makes the rest of us better of.
Having a little help like the child tax credits allows them to get their head of the water and make better decisions for the medium and long term. (like improve their education, take better care of their kids, etc.)