It's Friday!!!!
Looking back on the week, what was something you're proud of?
All wins count -- big or small!
Examples of 'wins' include:
- Getting to all your meetings on time
- Starting a new project
- Fixing a tricky bug
- Cleaning your house...or whatever else that may spark joy 😄 🎉
Latest comments (52)
This week, I actually understood this week's lessons at Lambda School on relational databases, SQL, migrations and seeding! I was nervous about going into the back-end unit, but I'm getting the hang of it. :)
Ha ha ha! Love it, way to go!
This week, I...continued working on a .md template generator CLI and finally got data returned the way I needed it in my biggest SQL query yet (8 window functions).
This week, I finally took the time to add
optional chaininginto a JS project (something I'd been saying I was going to do for ages but never found the time). Out with the:and in with the
😄
This week, I...
This week, a team I help to coordinate started a 11-week project building cohort with developers from 70 countries to help them put the skills they've been learning into practice....and to learn more!
This week, I had the first guest on my podcast where we talked about websites, social media, and content ownership (which greatly relates to Ben's win this week).
Listened, and subscribed on Google Podcast. Great work...keep it up. Looking forward to the next episode.
Appreciate it Matthew 🙌
This week, I discovered dev.to, I wish my LinkedIn feed looked like this! A real dev community!
This week, I... told my team that I handed in my notice to start a new job next month. A bit of a weird one, but one that I dreaded doing. Just glad that I did it.
I know that had to be tough. Congrats, and good luck (and I mean that in a good way). Ending something stinks, but that's behind you so now you get to start something new...and that's almost always exciting!
This week, I came up with a new way to prerender one of my projects on the fly!
This week, I created my first merge request in our internal gitlab. We've been using gitlab for a few weeks now, so it's quite new. Also we don't have a code review culture in our team, we just trust each other to write reasonable code.
So when I changed an important feature ("updating a document means overwriting the content BLOB" becomes "updating a document means creating a new content BLOB") I wanted my colleague to review my changes. It turned out to be difficult because I changed some lines here and there, I did not even wrote a new method.
So how do you do review such changes based on a diff? Much of the context is missing!
I also tackled some defects and wrote some integration tests that increased our code coverage. Yeah!
And how do I use this giphy-link?
This week, I was added as a maintainer of Gridsome. A static site generator for vue.js and also got a lot of positive feedback about my last article!
My Workflow And Tools That Help Me Speed Up Productivity
Egwuenu Gift
Whoa! That's awesome!
This week, I...
Made some more modifications to my notepad web app (link -boiling-plains-87481.herokuapp.com) and it is fully functional to the point it is uploaded while also being mobile responsive, I plan to add on authentication,individual notes in the future soon.
This week, I...created my professional landing page for my services.
joseg.tech/
Everyone single dev should have one of these IMO.
Very cool!
This week, I... delved into Jest, a unit testing framework for Javascript as a potential testing tool for my Javascript projects.
This week, I... taught myself how to use Firebase.
Ah man...that's me next week. You're ahead of me! Any recommendations or links? Thanks!