This article codifies general power structures within organizations: who trumps who when making software decisions in an org and sells that status quo as some sort of useful rule of thumb, when it in fact has no utility at all.
NYC apartment’s lack of square footage is going to make it super inconvenient to store the containers as you await the next delivery and container pickup.
Nope, I’m reading the actual article and using the author’s definition of innovation: creating technology that makes our lives better as human beings. Not a small group of people making something that makes them a ton of money regardless of it being innovative as per the definition above.
I think on average you're right. As the project grows, these generators lose some of their initial value and speed.
If I were to use something like this, it'd be for rapid development initially for prototyping purposes. Then I'd transition to something more bespoke as needed.
If you know all your requirements up front, then starting bespoke from the beginning may be the better route.
Stop thinking about work as something you do from 9-5. Start planning your day around a more organic schedule. I work in 1-2 hours spats throughout the day, interspersed with working out, cooking, reading, watching youtube, etc. You need to integrate your work and life, rather than thinking of them as separate to get the most out of working from home.
It also demonstrates how disconnected from the average person he was if he almost only saw OSX, when the market was 95%+ Windows.