ππππ
Looking back on your week -- what was something you're proud of?
All wins count -- big or small π
Examples of 'wins' include:
- Getting a promotion!
- Starting a new project
- Fixing a tricky bug
- Survived a meeting that could've been an email π΅
Happy Friday!
Top comments (9)
Will be applying to the Community Program Manager role at DEV today! Wish me luck!!!
All the best! β€οΈ
Thanks Fayaz!
All the best, Francis!
Thanks Hemapriya!!! :D
One of my wins this week was publishing Edition #3 of a weekly series I've been building called Dev Opportunity Radar.
A few weeks ago, it was just an idea I wasn't even sure anyone would read. This week, I had people discovering opportunities through it, applying to them, and community members sharing opportunities and resources that ended up being featured in the edition.
Seeing it slowly grow from an idea into something people are actually finding useful has been really rewarding.
I also published an article about how communities have shaped my own journey, which felt meaningful given how much of this week's edition was driven by community contributions.
Also, I was invited to join The DEVengers this week, which was a pretty nice surprise π
Definitely one of my favorite weeks on DEV so far π
Did some experiments with AI and Software Engineering (SWE) that might be useful in the coming days (won't replace devs, rather empower them even more). Hint: it's about how to use some very low cost and/or open models to automate parts of SWE better than high cost models if you're good at SWE yourself. I think we all should experiment with AI that empowers devs, as opposed to acting like big tech. that are trying to replace devs. I'm calling this SWEA (SWE Automation), which is an antidote to Vibe Coding - here your SWE knowledge and experience will be empowered and enhanced by AI.
Posted a DEV article in my Short Series on AI Slop (another one in the draft).
Had an spiritual epiphany that'll likely have significant impact in my life going forward.
π₯°
My win this week: a Docker Compose PR from a Scarab Systems field test got merged.
The bug was a clean boundary problem: Compose was validating typed fields before unresolved ${...} interpolation variables had been discovered, so the validation phase was firing too early. The merged patch keeps the repair narrow and restores the right order of responsibility.
Small patch, big proof point. This one felt good.