Swapped my tool bag for a keyboard a year ago. Celebrating my first year as a #SoftwareDev π. Grateful for every bit of this journey. From 10+ years as a maintenance engineering to a fresh year in software. Grateful for this leap. #buildinpublic
I don't believe the people who write they ship in a week. I would never pay for a product that is ready in just one week, because then I would program it myself.
I write comments when I code! However, only if I have debugged over the same place three times before and do not understand it again and again π¨βπ»π¨βπ»π¨βπ»
Don't promote your product directly, just write what you do. Share your key learnings and technical info. Product info rarely gets good engagement. π
That feeling when you can roll out a few features again is priceless. It's like unwrapping small gifts every day instead of waiting for Christmas. ππ
Day 18 of #100DaysOfCode - I dug a bit into the selective.js library. I implemented this into my side project because I use it at my job and I want to learn more about it. Seems like a really great tool for drop-down.
Day 17 of #100Daysofcode - I continue to work with the select service drop-down on my project. This include CSS and JavaScript. Hereβs an example of how it looks.
Day 16 of #100DaysOfCode - going to continue to style the services drop-down box to make sure itβs centered correctly. Seems like it will be all about #CSS for today.
Today is blog night again. I'm writing a few blog articles again that I'll publish under the use cases for LogHive (loghive.app). Of course I'll prepare the entry as a blog entry so that I can duplicate it via #pSEO. #buildinpublic#softwaredev#seo
When you learn a new framework or programming language, the question is always how best to teach it to yourself. I have become accustomed to use udemy.com courses. A lot of the content is very well prepared and you get a quick overview. #buildinpublic#softwaredev
Today I had the first "real" test of my online badge in loghive.app. One of my projects went offline for the first time in 3 years. Let's go to the error analysis which events were streamed until the downtime. #buildinpublic#softwaredev