What was your win this week?

My this week's win was getting featured in your post.

Starting a new job on monday after 6 months of rest!

Practicing a lot of regex \o/

Worked through a complicated JavaScript exercise on stream that I had gotten stuck on previously!

I have a 3 weeks strike on writing 🎉

I recently wrote a post that has more comments than the most liked post on DEV, in just 2 days!!

Stop Using .env Files Now!

Gregory Gaines ・ Sep 19 ・ 4 min read

#javascript #webdev #node #productivity

More understanding of Haskell

My first WordPress plugin, for Gutenberg, but that's something.

wordpress.org/plugins/tsparticles-...

Sometimes it was hard to understand the documentation, but I at least I did it.

After that I started using SVN for updating it, and it was my first time using SVN in a real way.

My most viewed post 'Adding PHP 8 to Laragon' just hit 42K view, probably will hit 50K by the end of next month. The post is read by 100 users each day on average.

Seems the post is one of the top search results for the case. Thanks to dev.to

• my first contribution to hugo notice has been merged!
• finally finished the book " Hugo in action"
• reviewed a new hugo theme
• updated jamstack.club with a few new themes (and fixed a bug on the way: now Github data are properly updated)
• submitted a PR to Papermod, the theme I choosed for my devblog

' was a nice week!

Make a good-looking simple webpage as a backend developer :)

I stumbled across Backstage.io

As Director of Infrastructure, I have a large and complex cloud platform that includes three product acquisitions and extrapolates into something like 20 different vendors and 3,000 containers running using kubernetes. That's a lot of mental gymnastics depending on the context of a given problem. This OSS package would help lessen the burden of knowing the nuances of everything.

So far I have spent ~ 6 hours prototyping an implementation and I'm seeing an incredible amount of value. Some of the highlights thus far:

• All the auth options. I went with Github given the core audience for this implementation but I could have easily went with my official SSO provider Okta as well. Google was also an option.
• Backstage pulled in all the users and groups from Github, that's less I have to implement or manage and I can easily reference the groups for access control of specific resources. (example: Contractors cannot have access to my production resources)
• I was able to define a few of my org's Github Projects, and aggregrated insights from: Docs, CircleCI, Github Actions, Pull Requets, JIRA, Codescanning, and Sentry.io errors, in addition to some custom context like links.
• I will be able to do the same for my deployed resources, both public facing and back-office.
• It's built in React and Typescript. My team builds in React and Typescript, enabling them to extend this if they come up with ideas for new widgets and views.

In short, this will make my 60-member engineering team's lives easier working across the complexities of our environment. When their jobs are easier, they're happier, get more done, and spend less time looking for a new job, I consider that very much a win.

This week I managed to decipher some old code (not written by me, either) to understand a data structure I had to generate data from.

Incredibly deep structure and obscure naming. I'm just glad I don't have to change any of it.

I tried 3 different backends to supply data to a simple Flutter app in its PaginatedTableData widget. Only Node.js + Express worked (also worked in React Native component), whereas PHP + Laravel and C# + ASP.net Core didn't, due to cors issue that I didn't succeed to handle.
Next time, I will try with Java + Spring and Kotlin + Spring (and probably Kotlin + KTor).

More skills with the ORM Prisma 🤔😄