If you want peak performance from your employees then leaders eat last.
189 karma · joined October 30, 2021
If you want peak performance from your employees then leaders eat last.
As far as the advice goes. No not really, lots of people are familiar enough with Kubernetes that it makes it the fastest choice possible for them. Engineers like to pretend that tech choices are oh so important and can be discussed in a vacuum, but really most tech choices are made once you know the people who are working on the project.
Pick stuff that is familiar to you unless you have a good reason to do otherwise.
An example: Business/product/whatever wants fuzzy search on a listing.
x2 says "I know how to do that. We just use Debezium and kafka to get the data into Elastic Search and then query it from there". Business/product/whatever says "cool, code it up". The infrastructure is a little difficult, but two months later a well tested good solution is in production, everyone is happy. Good job?
x10 says "how good does the fuzzy search need to be? Elastic Search is king, but Postgres can do it too". Business/product/whatever says "I don't know". x10 engineer codes a demo in 2 hours, shows it to business/product/whatever. Business/product/whatever says "that will do, lets ship it". The day after its shipped to production, noone ever talks about fuzzy search anymore.
Noone is every consistently x2 or x10 or xWhatever. Sometimes x2 is the best you can do, but other times you can do much much better. The trick is usually to be on the lookout for it.
If everything needs 5 databases, 4 queues, 3 caches and all of this is written in 7 different languages, then yeah I guess cloud is the way to go.
If you just shove shit into postgres and pull it out again using something like postgraphile then I don't think cloud does much for you.
The Flipside of the "computers gets faster and faster"-argument is that more and more can be done on one machine.
Compute supply is growing faster than demand. Today's apps are not that much more complex than the apps of 10 years ago, but computers are much faster. Human beings read and type at the same speed today than 10 years ago so I don't really see this changing massively.
Obviously all the BigCos listed can't run on one machine, but a very large percentage of stuff can.
Wages does not count as cost of goods sold, so who cares about a couple of extra hires? Funding is easy.
Also you severely underestimate the amount of work that goes under DevOps. Everything from build servers to test and security infrastructure is usually handled by DevOps. It's a massive surface area and it would be way worse without kubernetes.
Probably not, that's really the point :)
Although I think the limit is significantly higher today. Monorepo tooling is orders of magnitude better than 10 years ago.
> I only have one humble request, if I submited 51k lines of code in January and my whole team submitted 68k, do not call me a "Least Effective"
Let's give him the benefit of the doubt and assume he works 10 hours 6 days a week. Of course he takes no bio breaks, doesn't eat or drink and is not required to attend any standups or status meetings or design reviews.
This nets you 15600 minutes to code. So even under these absurd conditions he has managed over 3 lines of code per minute. What a god.
This is the mistake, web/desktop app programming is exactly a place where you throw stuff at the wall and see what sticks. It does not matter how great your app is if no one is using it. Conversely if your app is successful you can always pay someone a ludicrous amount of money to fix it, software is nice like that.
Databases and operating systems are a completely different beast. In those domains things get so complex that proper engineering is essential and in those areas you also tend to find "better" engineers. But web and desktop applications is like building tool-sheds, engineering rigor is irrelevant. It matters when you build sky scrapers though.
What do you mean? Like cars, houses, restaurants, groceries and almost literally everything else on the planet? :)
In all of your examples you keep mentioning that they either remove or change something you like thus forcing you to do something to keep up. That is the real problem, they are making changes that the user is forced to deal with. If all of these changes were fixing things you were legitimately annoyed with then you would be a happy camper, but that doesn't seem to be the case.
The metaverse is poorly communicated. Revolutions start at level 1, but communication sometimes start at level 25.
level 1 for smart phones: Read email/chat while waiting for the bus
level 25 for smart phones: A large economy with global behemoth corporations built on the premise that everyone has computers in their pockets
Level 1 for metaverse: You can now work from your couch/porch/beachhouse/bustop as you don't need your screens
Level 25 for metaverse: Everything running in 2d on computers now gets translated to 3d in the metaverse, a new set of global behemoth corporations. Massive implications for code, data and anything big or complicated (think structural blueprints)
Whether revolutions succeed or not is decided by teens and twenty-somethings, not the 30+ crowd (parents dont get it, not now, not ever)
The real challenge here is creating hardware that is cheap and good enough that teens can and will buy it, just like with the smart phone revolution, if you get 90% penetration with the teens then the rest of the world will follow.
Quest2 costs about the same as one decent screen.
I am not a business analyst, but from where I am sitting it seems like they've at least got traction.