That said, the tedious refactors are a real pain. I think we all hoped that rustc would be smarter by now. It has gotten better but it isn’t there yet.
393 karma · joined September 28, 2013
That said, the tedious refactors are a real pain. I think we all hoped that rustc would be smarter by now. It has gotten better but it isn’t there yet.
Staying in a hard VO2 interval or pushing through on those long threshold efforts is an actual mental exercise. Don’t push the belief onto people that staring at a wall in Z2 is giving you some gains. If it works for you then go for it, but it’s a wild mentally that thinks a physically easy ride needs to be hardened up.
Although sometimes “memorization” doesn’t happen because you sit down to do it but rather that you keep using the same things over and over when solving problems that they become internalized. I find that to be a more fruitful path towards understanding that I don’t want to call memorization but it is.
https://staffeng.com/guides/what-do-staff-engineers-actually...
https://staffeng.com/guides/staff-archetypes/
I think it all depends on who you are and what your team needs.
I was initially amazed at this when I was in graduate school, but with enough experience I started to do it myself. Handwaving can be a signal that someone doesn't know what they are doing or that they really know what they are doing and until you are far enough along it is hard to tell the difference.
> If you're a leader seeking to increase employees' motivation, what can you do? Leadership experts Allan Cohen and David Bradford offer some suggestions. [4] In Influence Without Authority they articulate a set of principles and frameworks to support the development of stronger working relationships and more effective collaboration.
Your comment is irrelevant to the actual article. You are responding to a straw man of your own invention.
In other words, if my friend is on the other side of the world and we can only communicate digitally, I need to bootstrap trust in a public key somehow and that is always outside these protocols. This is specifically called out here in section 4.1 and I'm pretty sure this is just a fundamental reality but I wanted to see if anyone had pointers to either a general proof of this or some kind of alternative.
Engineering management is more on the management of people and engineer leadership is more on the management of products/projects/systems.
I’ve been trying to figure out how to temper my natural tendency to go all-in with the reality that everything has some shit that sucks. I can understand the hope that there might be some psychological ease associated with dissociating yourself from the vision.