761 karma · joined August 5, 2017
When a single number becomes the single most important number the country measures, everything else takes a back seat. And that doesn't mean other things don't get any attention... it's just that spending time and money on things that don't have a direct (perceived) effect on GDP doesn't much happen.
* If possible, set up your home office next to a window. Open the window whenever weather permits. I don't follow the "20-20-20" rule for eyestrain relief, but it's relaxing to just stare out the window for a few minutes when I need a mental break.
* Set up your keyboard, monitor, and desk correctly to prevent RSI, back problems, etc.
* If you're working, work. If you're not working, be somewhere other than your work laptop/desk.
If I make a window of bulletproof glass, it's a lot harder to compromise.
If I surround my building with a wall topped by razor wire, it's a lot harder to compromise. (Unless, of course, I'm making an action film.)
Depending on what or who I'm protecting, I might find these solutions very valuable. Similarly in software, depending on what or who I am protecting, I might be very interested in various security measures.
So far, we've managed to escape an incident where bad actors have compromised systems in a way that's led to severe loss or harm. People are terrible at evaluating risk, so people tend to assume the status quo is okay. It's not, and it's only a matter of time before a bad actor does some real damage. Think 9/11 style, something that causes an immediate reaction and shocks the population. Then, suddenly, our politicians will be all in favor of requiring software developers to be licensed; liability for companies that allow damages; etc.
Also, the masses usually end up in just as bad a pickle as before, if not worse. (Reference: most revolutions/uprisings.)
And people will (continue to) adapt, no matter how bad things get. Living with parents longer, finding roommates, cutting costs elsewhere.
Maybe fine for an e-commerce site or game, where the stakes are measured mainly in lost revenue/customers and a team of engineers burning the midnight oil to sort the problem. Not so fine for spaceflight.
Now the Federal spigot has dried up (well, is back to normal) and interest rates are higher.
It means that you need to be responsible for yourself, and not allow thoughts like "I'm a valuable employee", or "I have too much seniority", or "my manager and I get along great" to convince you management won't lay you off or fire you or that they owe you anything.
As others have said, the employer-employee relationship is first and foremost a business relationship, i.e. transactional: you work and they pay you. When that relationship doesn't work any more for one side or the other, it ends.
It does often happen, of course, that professional friendships or even personal friendships develop. You are, after all, spending a lot of time with your co-workers. But don't think your good relationships or friendships will help if the business decides a layoff is necessary.
What you did wasn't "pair programming", it was an argument.
Bragging rights fits in here as well for a certain cohort. "Oh, you got 5.551Ghz, not bad but I'm at 5.5511Ghz".
Another classic example of this is uptime bragging for some linux fans, as a way to both one-up each other and to one-up the Windows community, which (more so in the past) had pretty awful uptimes due to various bugs and the need to reboot after making config changes. (We used to joke: "You have moved your mouse, please reboot Windows for this change to take effect.")
I think most people in this kind of community though just enjoy tinkering and maximizing performance/whatever.
Recently there does appear to be more noise around employee/worker benefits (including wages), hence things like the striking screen actors and auto workers (and attempted strike from railroad workers, who have shockingly terrible benefits), and renewed interest in unions.
The health of a country ought not be measured solely by its GDP and financial markets.
Whereas MongoDB is "simple".
(Two simple examples: (1) how do you measure the productivity of a lead developer who spends much of his time mentoring, pairing, and helping the team deliver working code? (2) Is a developer who commits many small PR's "worth more" to the company than a developer who commits fewer, larger PR's?)
I 100% agree with the overall idea that we aren't able to deal well with the consequences of what we've created with social media.
I'm not saying Ladybird "needs to" have all this, just putting some of it into context. And it's no slight to the project either; they've managed to get a lot working with a paucity of person-hours.