Week's digest #3: What happened last week in the web?Week's digest #3: What happened last week in the web?
This week's digest is more focused on non-technical tools because I have not been programming. It has things like how to evolve a process that works in teams, how to influence without authority, how to coordinate. But it has at the end some nice Aww making links to spark our joy
What I am thinking? #
There are so many things that I would like to do or that land on my plate at work. Because I can't and don't want to do everything. I ask myself the following questions to help me prioritize and organize my time:
- What do I want to own?: What gives me joy and also makes an impact on the business and customers
- What do I want to collaborate on?: What I like, but there is another person or people who are more passionate about it
- What do I want to be an observer?: Nice ideas I'd like to see happening
- What do I want to delegate?: If there is someone who this challenge would excite, like, or want to do it, then I would engage them
- What do I want to drop?: Whatever drains my energy or does not produce an impact
- What is in the important/urgent and important/non-urgent axis?: important and urgent get priority, then come important and not urgent.
Finding answers for this, amidst feeling passionate about everything and not wanting to drop anything, can be hard. But it is worth doing, especially because it helps to keep a good work-life balance, which will end up making you a happier person.
Ideas to bring to my project #
This blog has a bunch of useful content for tech leads or anyone in a similar role. What I liked about this blog post, is that it takes a UX approach to bring new processes to development teams.
This is useful because, we, developers are humans too, are users too, and have in a normal day a lot of things to take care of. And introducing a new process, a new way of working usually works best when you do it together with the rest of your team.
I have been doing this for a while already, mostly intuitively, but this post nailed it. I did a diagram for me, to remember, which I share here with you.
We all find ourselves in the situation, from time to time, when we want or need to influence others, but have no authority for that. I would even argue, that if your approach is to be more like a leader, instead of a manager/boss, even if you are in a position of authority, using tools like these will come in very handy.
What I liked about this blog post, is that it proposes to do the first step that the model Non-Violent Communication suggests: Understand first, or in the NVC model: Listen first.
How many times didn't I come to a new team, project, or situation, where I saw some non-efficient - to my eyes - process, and I proposed directly a solution?, and out of all those times, how many times do you think I succeeded?... Don't answer.
In the post, the author expands on what to do after understanding, but what I will remember and I am now actively practicing is: Understand first. Once I nail this consistently, I will come back to it, and read what is the next step.
Software development is a team sport, and if you, like me, are mostly working in a large-enterprise field, you will find yourself needing to collaborate across different teams.
If one thing I have learned from reading, learning, and experimenting over years with psychology and sociology theories, is that labeling things helps to address the ambiguity.
This blog post goes definitely to my toolbox, first because it gives a definition to collaboration models I have used in my career, and second because it adds new useful ones. It will come handy when I find myself in situations where a new collaboration model needs to be established.
I want to read more #
I am one of those people who goes and reads things like EcmaScript specs. This blog post goes a bit into that nerd direction (note that my definition of nerd is positive), I am not sure if I will actually find the time, or when I will, but every time I read and understand how rendering engines in the browser work, I become a better developer. And that lights my fire.
For my toolbox #
Is a random feedback text generator, which I will most likely come back to, whenever I didn't get yet the copy from the copywriters, UX, or whoever decides what copy to write in a specific part of the web app I am working on. It gives you messages like the one below to use for example in a loading message.
"Time to take a breathe and smile, how beautiful you are By Alfathony" - Perhaps I will add this as an Easter egg for screen readers without telling anyone.
Pretty, Aww or probably useless #
Hakim El Hattab is a Swedish developer who is experimenting a lot with CSS, animations, among other things. And his last experiment is a lovely, animation to show in which element you have the focus. Probably something we won’t bring to our projects, but will make you smile at least :)
Video animation for a mental break #
This is a beautifully made stop motion animation by Tomohiro Okazaki, with matches. If you will watch it, find some nice electronic song of at least 7min, to pair it with, sit back, and chill.