Nerds, tune in next week!
I'll be with Penny de Byl (@penslayer), Dylan Meeus (@DylanMeeus), and Jasmine Greenaway (@paladique) answering your questions.
https://t.co/PnbfGBtQTL
My “author interview” for my book “Functional Programming in Go” is out! https://t.co/ZaODJmgmbn 😁
And the book itself is also ready for pre-order on Amazon 😎https://t.co/NjQ7KOog87
@Lynx_Eyes @davefarley77 For any management role reading this. The way to avoid that is to provide context on top of "can we talk".
e.g: "Hey, can we talk? I need some input on {xyz}"
@chrisrickard Writing / communication - you'll be writing a lot of documents throughout your career, especially as you move up and start working more on system design problems rather than writing code.
@shanselman In a job interview, I said "tree" but then spelled it out because I was pretty sure I was saying it wrong. I think it's actually "try" though.
@rakyll Honestly, as someone with pretty swamped calendar at Amazon, this is often the only way to make sure that I have the time to read your doc and provide meaningful input.
@rakyll I know what you mean by that (care about the project / tech etc). But to nit.. care about people (as a manager) is a prerequisite. If a manager does not care it is a bad thing for that IC imo.
@copyconstruct I value EMs who at least have coded for some time, just so there is a shared jargon and understanding of what building software is like.
I can’t imagine there would be an IC -> EM who thinks LOC is a good measure for example.
Just seen the new Dr Strange movie and I can’t help but wonder.. are there some serious fans of Mortal Kombat involved with this one? 😅 Definitely expected to hear a voice shout “Fatality!” In some fight scenes 😆
@smdiehl@mxgxw_gamma Cambridge Analytica might be close to that though? (Not a recommendation engine, but an algorithm based on social network data anyway)
@GergelyOrosz Also, on that topic, I hope no one takes these estimates as a drop-dead date. Anyone who has worked in software for a couple of years should have figured out not to do that 😅
@GergelyOrosz There's also a difference between estimating a task in a sprint, and a project months out for delivery. Further out in the future == lower precision.