software development

My ideas and urge to keep implementing all the fancy stuff could potentially endanger the stable release of the Writestreak. I've already done implementing some of those, but others are still in progress. It might be easier to take a step back and stick with the basic functionality first.

I'm an avid advocate of green tech thinking. So obviously I want whatever I code to be as efficient as possible regarding resource usage. My current website and writing platform produces only 0,08g of CO2 on page load. According to wesitecarbon.com that is less than the emissions of 93% of the sites tested. I definitely wish to keep my new platforms emissions at the same level. Going any lower starts to be quite challenging. 

I guess it's good enough to show. I've got most of the issues sorted out to the point that the site is already usable for demo purposes. There are still a lot of all those little things I'd like to iron out. There is also still a lot of work on the backend side. But the basic functionality is there and it doesn't look half bad.

I don't think there will be better time to release it to the wild. If I keep it to myself I just keep refining it over and over again. Trying to reach perfection is sure way of never releasing anything. Trust me, I have plenty of those projects.

I'm no stranger to JavaScript. I used to write it quite a lot 15-20 years ago. I even wrote couple of frameworks for it. So it shouldn't be that hard for me to work with it after all these years. (I have done some occasional JavaScript coding during the meantime too.)

The language itself isn't the problem. Even if there has been a couple of major iterations of it that came out since my prime time. It's just syntactic sugar, easy enough to pick up rather fast. In many ways it's a lot easier to do things just by the vanilla JavaScript itself than it used to be.

The famous quote from Edison about his success in finding multiple ways of how not to so a lightbulb pretty  much sums up my todays progress working on the writing platform. In a sense I didn't make any progress on it today despite working on it for several hours. I did however learn a lot about modern JavaScript and how not to do things.

It wasn't just a talk, I actually went ahead and started prototyping an alternative social streak writing platform. And of course I couldn't wait until the weekend! I've already spend a few hours during the week to setup something simple.

Getting up with the basics is easy. I already have fully functioning platform ready where you can register and login, write posts and comment them. There is even a favourites feature. Then there is own, recent and popular posts listings too.

During my professional career I have held many different roles. They all have required certain level of education which I have mostly acquired through self learning. While somewhat related there has been quite a spectrum of what I have done. But one thing has remained my core competence: infrastructure management.

Infrastructure as Code (IaC) has become a much needed standard managing any non-technical infrastructure setups. IaC means having the infrastructure definitions written down in files and bases on those files the infrastructure can be modified or even recreated as needed.

Documenting a software project is always one of those chores nobody wants to do. For programmer the code itself serves as a documentation .An accurate one unlike the separately written one which is always out of date anyway. Non-technical persons also wouldn't understand the technical documentation much better than the code itself.

After the latest update and change from cowriters to writelier it seems I have been writing posts from the future. For some reason the posts show the next day as their publication date. I haven't checked whether this is only an issue with posts written later in the evening (which would kind of make sense) or all posts regardless the actual time of writing.