Googled their resume and it’s copied from another LI page…

I liked www.ece.uvic.ca/~frodo/cppbo... when I learned. Learn by doing

Always need a back door if you go all in on gitops

Going 130 feels too much when the speed limit is 100. But people typically go 80 in a 60

I really liked his post in how to dive into large complex code bases. Still in my bookmarks bar

And as a TL, there’s a bit of if you put down ambiguity you are admitting you are unable to scope and think through the project enough

I think for me, the lessons are to choose the team carefully, to make sure there’s enough people in at least the owner camp for the given project. The planning one is always hard, hours dedicated to ambiguity is difficult to prioritize against other concrete projects

It’s just something that I’ve been dealing with recently, where managers ideally want predictable planning and resourcing. And there is a less committed or less experienced engineer that is more or less only effective with a concrete task based roadmap. Iteration is ofc more natural

I’ve been wrestling with the individual tasks one a fair bit, lmk if the authors recommend a workaround. Individual tasks are nice if all task items are known or discoverable in advance

If you can’t tell, it’s swollen enough to crack the case.

I had a friend recently have his house burn down from an e-bike he bought his kids. It’s all making me a bit nervous from all the batteries and power strips we have in the house

I am finishing up leading a multi year multi team project. Wrote about the things I learned for this one, which all come down to “basic” project management skills

writing.samsonhu.com/tactics-for-...

His last mark in life

The alleged shooter had everything set up for a trajectory of doing something great in his life. As his bucket of illnesses took hold, he may have felt his window closing. Losing his ability to work and make impact may have been imminent, and he carried out his hasty manifesto and plan best he could

When I try this approach in our GitHub I get a bunch of nerve conflicts as I try to fetch and rebase the child diff after the parent is merged in. I think it’s because we squash and merge, so old changes are then rebased against a future squashed commit

and bag / bAg aparently

process / prOcess