Among the most powerful of team building and communication tools a leader can have is the retrospective (known in some circles as “postmortem” or “root cause analysis”). During the retrospective, the team talks about as a group and without blame of individuals what went well, what didn’t, and how they can improve.
It’s a month of lessons into our #learntocode group (we took a few weeks off over the holidays) and I’ve been learning a lot about myself, my students, programming and how people learn entirely new concepts.
When picking who you’re going to go into the fray with…
Find a leader who understands that trust is important.
Also find one that knows it is earned, not given. They'll likely understand that it’s easily broken, but double check.
Note: This was written shortly after GiveCamp. It's been sitting in my drafts folder for 4 months, for which I apologize
In July, I had the chance to go to the 2017 Cleveland GiveCamp.
GiveCamp is a annual event where ~200 programmers and designers get paired with
a collection of non-profit organizations to help with their technology needs.
Most often, that means a website that allows for donations, contact forms and
photo galleries of what the nonprofit does. This was my 7th GiveCamp – I
attended in 2011, 2012, 2014, 2015, 2016
and Seattle in October 2017 as well.
Recently, I read an article titled
Time for Makefiles to Make a Comeback
which reminded me of a fantastic UNIX tool that far too many people view as being scary.
One of the things that gets talked a lot about in our industry is "impostor syndrome" – basically, the inability to internalize our accomplishments and living in persistent fear of being exposed as a fraud.
What are some career mistakes you've made or observed in others? How do you avoid them? #devdiscuss
— The Practical Dev (@ThePracticalDev) September 6, 2017
For the past 2 weeks, I’ve been experimenting with the idea of time blocking my day, and am happy to say that for the most part, it works.
The 3rd factor of a 12 factor app is configuration stored in the environment. Now that it's in your environment, how do you access them?
Recently at my job, one of the other software developers was talking about how they had a trick where you’d land in a vim session on every login.