What was your win this week?

I published my latest dev.to article directly from my own WordPress editor using the plugin I built for the GitHub Copilot CLI challenge.

Small win on paper — but a real one.

For the first time, I just wrote, hit publish, and the whole pipeline worked: formatting, sync, deployment. No manual export, no copy-paste, no friction.

I could simply focus on writing (ironically, about who we’re writing for 😄).

My win this week was publishing something before it felt perfect.

I tend to overthink, refine, and wait... but this week I shared an article about why I started creating bedtime stories for kids.

Not a huge launch.
No big announcement.

Just pressing publish.

Sometimes consistency is the real win.

I've been meaning to make some changes to an API, but the fear of breaking things for customers has kept me from updating it for months. I kept thinking and thinking if I had missed something, did a lot of testing and analysis, and did it all over again from the beginning. This week, I finally pulled the plug, and it went up to the production server, and it worked!

I'm very happy about it because that update was keeping me from shipping a new service I need to offer to my clients. Hopefully, I can start selling this new service and increase my revenue so I can hire some help to run the project.

It’s Chinese New Year this week, but I still managed to publish a few articles on DEV. This marks my second week on the platform!

I built a multilingual programming language that can also run on the web, thanks to WebAssembly (WASM). This is one of dream projects and I am glad to see it working. I also published a dev.to article about this.

This week, I submitted my project for the Github Copilot Challenge. I got a lot of reactions which has made me eager to explore this project further.

I also got awarded a Top 7 badge for my recent post: Why Learning Basic Robotics Made Me a Better Software Engineer in the Age of AI which I am super grateful for :)

Have an awesome end of week everyone!

My biggest win this week was letting frustration dictate my engineering output.

I sat down to write a standard article about the AI productivity crisis and the difference between chatbots and real execution.
Halfway through, I got incredibly frustrated. The draft felt like just another theoretical opinion piece.

Instead of publishing it as it was, I scrapped the theoretical approach.

I went down a technical "rabbit hole" if you will and wrote a Python script, and pulled raw data directly from the Yahoo Finance API to prove the market reaction to Anthropic Claude Code.

I documented the raw terminal logs and the exact AWS architecture required to build actual systems of action. You guessed it : It really didn´t work for the LONGEST time.

The published article on dev.to was just a "byproduct."

The real win was refusing to publish what I consider "fluff" and forcing myself to build the verifiable proof. The friction created the value.

This week we resisted the urge to build our internal social media scheduler and will instead use an existing third-party solution. For now. 😀

I Finished my CV for a Developer Relations role at Expo.😀

Over the past few months, I’ve discovered how much I enjoy learning new tech and turning it into simple, practical tutorials!. I’m excited about building a career where coding and teaching go hand in hand.😊

This news, of course 😄

A New Chapter: DEV is Joining Forces with Major League Hacking (MLH)

Ben Halpern for The DEV Team ・ Feb 18

#news #devto #hackathon #discuss

But also, I went to a local pitch event last night and came back feeling quite inspired by all the founders and their businesses. Learned a bit about space debris and made a few connections.