Press review #6

2 years after my last press review, I’m rebooting the format. I feel my blog reading has not been great lately, I want to learn a bit better.

  • An nice article from Kent Beck explaining reasoning behind TCR (Test && Commit || Revert). I like how small changes are valued for their stability and simplicity. I admit, I doubt it can be scalable in most companies, but it can be really fun to try at a coding dojo.

  • Every software practice is an opinion, thoughts leaders are more opinion marketers. In his talk Hillel Wayne explains what can be saved thanks to empirical studies on engineering practices. 3 points : tests are just as useful as parachutes, code review are great, all sleep and no stress are the most effective ways to build software.

  • Also, there’s a new release of postgres and it looks pretty awesome, can’t wait to try it !

Tweets !

“Mistakes are expected, respected, inspected, and corrected.”

Lara Hogan's Resilient Management, reading notes

I read Lara’s book carefully taking a lot of notes compared to other books. It is filled with 101 management, wise and practical advises for everyday life as a manager. Even I, being a developer aspiring to management positions, could get some really good insight to what to expect from a manager. My notes consist of quotes mixed with my own comments. Writing the post allows me to fixate this knowledge somewhere for future reference.

My notes

A manager works around 4 dimensions in a team:

  • Resiliency
  • Human growth
  • Delivery
  • Cross-functional strategy

Two busy weeks

This is the story of two rich weeks I’ve just been through. I’ve attended to three events in a row, depleting all the energy I had, but also teaching me so much!

It all started Tuesday 14th with a conference day with the whole tech team of Malt. It was the first time all of us gathered and shared knowledge on our different specialties. We had the chance to listen to brilliant Nickie Roudez explain CSS grids, Aurélia Amalvict showing the power of K-means to explore users topologies, Nicolas Demengel explaining how hexagonal architecture works, etc. It was a perfect opportunity to discover all the team members I haven’t met so far (we’ve more or less doubled in the last 6 months) and explore new challenges.

I’ve captured the whole team during a session, aren’t we beautiful?!

Newcrafts 2019, Paris

Speaker's notes : discover event-driven programming

General advice:

  • Make sure to have a bottle of water nearby
  • Open xrandr options before it starts
  • Open pursuit before it starts
  • Changing the police is CTRL + 6 and CTRL + = on alacritty
  • Find a high contrast theme for alacritty (no light green or yellow)
  • Prepare some slides to tell the audience what they have to do
  • One screen, one window
  • Purescript ain’t rocket science but make sure to explain basic syntax when introducing it (pattern matching, function signatures, records, hof, etc.)
  • We’re using purescript, but it can obviously be done in any language

Next up, how should I present each steps:

Event storming

Quick Recap on The Manager's Path

The Manager’s Path is the reference book if you want to learn about engineer management, that is anything ranging from a mentor position to being CTO. The book emphasizes on the obvious state of becoming a manager as a technical engineer: you will code less, you will have more responsibilities and your capacity to lead others will be key to your success. Here’s what I learned by reading it.

Mentoring

The first step to enter in a manager’s position is to mentor an intern or a junior dev entering the company. If you are assigned to the task, don’t discard the importance of taking care of her. Take time and attention to:

  • Provide clear goals: how do you expect your mentee to perform
  • Provide guidance and reassurance: entering a new company can be disturbing and stressful. Your action can make a change
  • Assess your mentee progression with regular 1-to-1s
Older posts...