I have shifted to a Tech Lead role for 2 months.
And I've already learned a ton with my team.
These lessons cover a range of topics, from coaching, planning, to technical writing and more
I'll keep sharing these hard-learned lessons on Twitter.
This ๐งต would be an index:
COBE v2: reliably use any DOM elements as markers & arcs. CSS transition, animation, filter, interactivity, ...all just work.
High perf, zero deps, still ~5KB. Coming soon.
My 2024 ElixirConf US talk Folding the Umbrella is finally online ๐ฅณ
Check it out to learn how you can get all the benefits of umbrellas with a much simpler project structure ๐
https://t.co/UlwriTK6zq
๐ง๐ต๐ฒ ๐ ๐ฎ๐ป๐ฎ๐ด๐ฒ๐ฟ'๐ ๐ฃ๐ฎ๐ฟ๐ฎ๐ฑ๐ผ๐ : ๐๐ฒ๐๐ฎ๐ถ๐น๐ ๐ช๐ถ๐๐ต๐ผ๐๐ ๐ ๐ถ๐ฐ๐ฟ๐ผ๐บ๐ฎ๐ป๐ฎ๐ด๐ฒ๐บ๐ฒ๐ป๐
You absolutely need to know the details. If a department head doesn't know their numbers, that's a massive red flag--they're not on top of their responsibilities.
But micromanagement is equally toxic. When you interrogate every decision and dictate every action, you strip away autonomy and turn people into cogs.
But micromanagement always signals that the manager has failed.
Micromanagement is a flashing warning sign that something's broken, and it's always the manager's fault.
๐ฆ๐ฐ๐ฒ๐ป๐ฎ๐ฟ๐ถ๐ผ ๐ญ: The person can't be trusted with decisions and needs constant direction. You hired wrong. That's on you.
๐ฆ๐ฐ๐ฒ๐ป๐ฎ๐ฟ๐ถ๐ผ ๐ฎ: They're capable but you won't let them work. You're the bottleneck, hurting good employees and preventing the company from scaling.
Either way, your best people will leave. People want autonomy. They want to contribute meaningfully, not follow scripts.
The Solution: ๐ ๐ผ๐ป๐ถ๐๐ผ๐ฟ ๐ช๐ถ๐๐ต๐ผ๐๐ ๐๐ผ๐ป๐๐ฟ๐ผ๐น๐น๐ถ๐ป๐ด
You can know everything without dictating everything. Monitor performance and hold people accountable without micromanaging their process.
If you can't figure out how to do this, get help immediately--a book, a coach, something. Because right now, you're being a terrible manager.
The goal is simple: Stay informed while staying out of the way.
The article below is how I do it:
The BEAM Book 1.0 just dropped!
400 + pages of Erlang/BEAM internals, message queues, processes, the works.
Pocket-sized, dumbbell-grade.
https://t.co/lrRuDnoBLQ
PDF & HTML free in repo.
Shout-out to everyone still on X keeping #Erlang lore alive at 280 chars. ๐ฆ๐
#BEAM#OTP
I was recently recommended this talk, and I really like it! If you develop software as part of a team and use git, check it out (and spread the word, it deserves more views ๐).
https://t.co/Gh4Ucsvpxa
FactoryBot is the quickest way to kill your test suite performance with Rails. Our HEY suite runs in <2 mins on a modern Linux machine with over 30,000 assertions. Against a real database! The secret? Rails Fixtures! They're setup once, txn-wrapped for resets, and insanely fast.