904 karma · joined November 15, 2007
I mean look at the success of Lil Nas X. Highly successful TikTok talent.
And that’s still not enough! Think of the value we return to an organization, and we’re only paid six figures.
Ya know, you’re allowed to fight for the absolute best working conditions as a worker.
You’re perspective reeks of some sort of corporate shill. Like I should just be happy to even have a job however shitty the working conditions. That perspective keeps developers underpaid and stressed out.
Well I think standups, on average across all possible developer contexts, are useless.
To put another way, standups are likely to be useless regardless of context.
But your job as a developer is to not have this happen. It’s nothing something that would be a nice to have, you’re supposed to always keep your team informed about potential gaps. The standup is designed to catch gaps but really that should be something you should already be doing.
Many American C-level execs at many large tech companies are huge pro basketball fans.
It’s 2019, software is the business. There’s no need for the redundant “business” prepended to it.
Because your average work makes like, what, 1/1000 of what an executive makes. But those 1000 workers help that executive earn very high compensation, but then I guess managing 1000 workers is 1000 times more valuable than the work those workers do.
But all that sounds like an idea an executive would invent to justify earning 1000x more than what an average worker makes.
Instead, I've seen mostly attacking a problem head on which involves a really inordinate about of planning, more planning, some execution, and then more planning. Planning so much, that timelines must be altered to make room for more planning.
That's been my experience though.
I believe the desire to blow through timelines planning instead of executing, is born out of fear and what I call the sensation of movement. Fear because management doesn't want to mess up and miss something important. The sensation of movement causes management to incorrectly perceive work is being done.
At the end of all of this, nothing is done because no one has done any of the work to accomplish it, they've only been planning.
We only have two options?!? That’s fucked up! This is not at all an okay state for software development ecosystem!
There’s a virtual monopoly on consumer applications! That’s the actual, real problem!
Of course he is. He is(was) about to help Google make many billions of dollars of which he and his team would only ever see a very small fraction.
God forbid an engineer get paid what he’s actually worth.
If anything he should’ve been paid much more. The automobile industry is a multi trillion dollar industry he’d be be disrupting.
Honestly, Google may have been paying him to “die” like tech companies do sometimes as rationale for acquisition: to eliminate competition.
Maybe he picked up on it and decided to move on.
Google doesn’t own technology he invented.
Feels slightly awkward as you have to make the associations in your head(Z to C, Y to B, etc.) but actually gives a way better sense of progress.
But if you can stomach that the thing may take years or even a decade, you'd feel much less like you were procrastinating.
In addition, if you assume that the thing will always be done piecemeal, here and there, or when you can remember to do it say like cleaning a room or organizing a thing, then that can also alleviate the sensation of procrastination.
The sensation tends to occur when you maintain a false belief that the things you need to get done should take hours or days instead of weeks or years.
Uh oh. So immediately you do understand that you have taken on the risk of potentially being unable to find any good(or bad) Rust engineers in the future, correct? Also they won’t be cheap as there won’t be many of them.
A smarter, business-friendly, future-proof approach would be to have done that in Java. Future you will want you to have done that in Java, but if you’re trying to retain good engineers maybe I get the Rust thing.
For example, if you're contracted to do a job, the client doesn't usually arbitrarily change the rates it's paying you unless you have some contractual agreement to do so(overtime, paid leave, etc.).
But that's built into the original contract during negotiations.
YouTube is just "here read this shit and do what we say and we can pay you or choose not to pay you or change what we pay you whenever we feel like it whether you like it or not"
Ye people like you kinda suck.
Unfortunately, you’re just now learning that maybe the new implementation isn’t “better” but that it’s just...new.
And now it’s slowed down the team too. I know it’s John Carmack, but still it’s not very collaborative nor empathetic towards your coworkers to plow through code like you’re the only one working on it.
Big tech will likely drag this out as long as they can.
Ha. I get a feeling there's alotta overpaid data scientists out there.
Clearly an ethical guy we're dealing with here. I'm sure this will all pan out well down the road.
idk the suits have a very different viewpoint; 30 minutes of downtime for a large financial system isn't fine. it can be very costly.