Senior Engineering Manager @Tubi Blog: https://xitter.cf/t.co/HKnOCr8qNn Past: CSSKatas: https://xitter.cf/t.co/f2tkj1LbLU #agile #leadership #tailwindcss #ruby #elixir #TDD #Emacs

Joined February 2014
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:
2
4
1
39
13,117
Yiming Chen retweeted
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.
75
210
16
4,197
225,615
说出了一个形容 test suite 的谐音梗:如测
1
485
Yiming Chen retweeted
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 🌂 youtube.com/watch?v=CKeYV_YO…
9
43
4,138
Yiming Chen retweeted
𝗧𝗵𝗲 𝗠𝗮𝗻𝗮𝗴𝗲𝗿'𝘀 𝗣𝗮𝗿𝗮𝗱𝗼𝘅: 𝗗𝗲𝘁𝗮𝗶𝗹𝘀 𝗪𝗶𝘁𝗵𝗼𝘂𝘁 𝗠𝗶𝗰𝗿𝗼𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 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:
2
2
17
3,194
Yiming Chen retweeted
Sorry but here’s a snippet to add that to any website: github.com/shuding/liquid-gl…
26
57
17
839
89,970
The BEAM Book 1.0 just dropped! 400 + pages of Erlang/BEAM internals, message queues, processes, the works. Pocket-sized, dumbbell-grade. amazon.com/dp/9153142535 PDF & HTML free in repo. Shout-out to everyone still on X keeping #Erlang lore alive at 280 chars. 🐦💛 #BEAM #OTP
4
41
3
143
8,402
Yiming Chen retweeted
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 😉). youtube.com/watch?v=1NoNTqan…
3
7
32
2,999
Yiming Chen retweeted
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.
26
37
14
602
87,651
"Ryan Singer (@rjs) and his Shape Up method is an incredible system that takes as input 'kludgy, clumsily scaled product org unsure about what to build and how' and delivers as output 'a focused clear thinking set of teams that has a rhythm, a method, and a purpose.” That's how @destraynor (co-founder of @Intercom) described the impact Ryan Singer and the Shape Up method have on teams. Ryan spent nearly two decades refining a product development approach at @37signals that helped the company build super-successful products with small teams. Based on these lessons, he wrote a book called "Shape Up: Stop Running in Circles and Ship Work that Matters," which describes a different way of working that an increasing number of companies are adopting. If your team used to run smoothly but is now struggling to ship great product, this episode is for you. In our conversation, Ryan shares: 1. A step-by-step approach to transitioning from Scrum to Shape Up by piloting the methodology with a single team before broader implementation. 2. Why traditional Agile and Scrum methods often lead teams into endless cycles of work without meaningful shipping milestones. 3. The “appetite-driven” approach to product development where teams set fixed timeboxes (usually six weeks maximum) and vary the scope instead of expanding timelines. 4. The exact process for running effective “shaping” sessions that collaboratively define projects before committing resources. 5. How to adapt Shape Up principles to your company’s unique context, even if it’s nothing like Basecamp. 6. Practical techniques for bridging the engineering-design divide by bringing technical and product perspectives together earlier in the process. 7. The powerful “breadboarding” and “fat marker sketching” techniques that help teams align on solutions without getting lost in high-fidelity details. 8. The clear warning signs that your current development process is failing before it’s too late to change course. 9. Proven strategies to implement Shape Up methods, whether you’re working in a startup or enterprise environment. 10. Why the PM role shifts upstream in Shape Up, focusing more on problem definition than project management. Listen now 👇 • YouTube: youtu.be/GF-yUANql0c • Spotify: open.spotify.com/episode/0z5… • Apple: podcasts.apple.com/us/podcas… Thank you to our wonderful sponsors for supporting the podcast: 🏆 @WorkOS — Modern identity platform for B2B SaaS, free up to 1 million MAUs: workos.com/lenny 🏆 @merge_api — A single API to add hundreds of integrations into your app: merge.dev/lenny 🏆 @airtable ProductCentral — Launch to new heights with a unified system for product development: airtable.com/lenny
9
19
6
198
127,188
I think design & architecture is even more important now. Once you’ve established good design in a system, AI will generally continue it. It still needs guidance of course. Without good design, the mess will just be made 100X more quickly. Then, all AI does is make messes & bugs.
2
7
2
26
14,038
A major part of software engineering is Divide-and-Conquer
1
271
Yiming Chen retweeted
Watch our full interview with Git creator, Linus Torvalds! ⬇️ youtu.be/sCr_gb8rdEI
1
11
2
48
38,676
Yiming Chen retweeted
In my "Tell me a Story" talk I recommended the book Looks Good To Me by Adrienne Braganza Tacke. It's a detailed exploration of code reviews, filled with a lot of practical advice on how to improve it, make it a more pleasant experience, and reap more value of it. Highly recommended! Give it a read, and you'll thank me later 🙂 manning.com/books/looks-good…
1
3
28
1,317
Working remotely has its perks. Now, when the code doesn't work, I can silently scream at my laptop without fueling office gossip about my impending meltdown.
3
16
2
126
12,933
Coffee is not an addiction, it's a necessary survival tool we developers use to procrastinate bug-fixing.
1
6
48
9,337
A solid 10% of being an engineering manager is asking two people if they've talked to each other yet
148
1,337
235
9,670
Forgot to mention—there's a new Oban Pro composition guide! It explains when and how to use batches, chains, chunks, and workflows: oban.pro/docs/pro/1.6.0-rc.1…
1
3
17
944
Yiming Chen retweeted
好的管理者要能做到既给下属整活的空间,又不要太多人『没活硬整』
1
6
1,694