Techstructive Weekly: Issue 3

Techstructive Weekly #3

 The week was really tiring for me for some reasons, was not able to work on the side projects. I actually spent some time with my family and cousin who came over the weeks for festivals. However, on the work side of things, I was able to learn a few things about NGINX, pdf parsing and product specific features.

The upcoming week(end) will be actually fun, as I finally have some free time to write some blogs, hopefully will be able to have some things to showcase and share next week about the things I explored or failed at those things.

Thanks for reading Techstructive Weekly! Subscribe for free to receive new posts and support my work.

Quote of the week

“The secret to satisfaction is to find meaning in the journey, not just the destination.”
- Unknown

Satisfaction is important in life, you need to understand the difference between your needs and wants. You absolutely have to give your best to satisfy your needs, but don’t go too hard on your wants, understand your intentions and the feelings of others as well. Don’t get too greedy on reaching the top, its should be about the process, about the art, about the journey, embrace it and focus on that instead.

Read

• A Pragmatic Workflow for Technical Writing:

  This article actually gave me the clarity to start my writing journey again, I seem to have lost touch with writing articles over the last few months, need to get back to the old routine of 1 week 1 article.

[

Mostly Harmless Ideas

A Pragmatic Workflow for Technical Writing

Read more

2 months ago · 16 likes · 6 comments · Alejandro Piad Morffis

](https://blog.apiad.net/p/a-pragmatic-workflow-for-technical?utm_source=substack&utm_campaign=post_embed&utm_medium=web)

• 20 years of blogging: https://jeena.net/20-years-blogging

  This shows how one must approach blogging as a developer, just be selfish, write for yourself first, if it helps others, that is the bonus and the reward for you. Don’t make your expectations too high, the rewards come over time, make a routine, just dump your thoughts if feeling a bit overwhelmed, it will help.

Watched

• NGINX Tutorial

• This gave me a good refresher and a bit more concise explanation of most of the capabilities of NGINX, I am running the Nginx Survival guide blog series, which I will explain the most needed and common uses of NGINX.

• RabitMQ from Boot.dev:

• The video demonstrates the basic architecture for the usage of RabbitMQ for developers. If you are new to message brokers and want to learn about backend systems, I highly recommend watching the clips of boot.dev.

• Problem with Tutorials: https://youtube.com/shorts/ZFi-LTpUGHA?si=qt2i80-68I9CwABB

  I can relate as a technical writer, how much stuff is lost while writing the blog. So many examples discarded, so many attempts hidden, so many words deleted. The final guide/tutorial looks so perfect that it might overwhelm the reader/listener that how is it possible to get everything right in the first place, in reality it is a result of failed attempts and trail and error.

• Tweet from Bill Kennedy about mindset of developers after the advent of AI assistants: https://x.com/goinggodotnet/status/1822298432813375760
  Really, this hit me hard, as a developer, we need to focus on solving architectures and problems and not limit ourselves in minor code fixes and feature implementations.

Learnt

• If you want to quickly get a JSON response from a locally running API, never use subprocess.run in python, this actually encodes the json response in a way that becomes almost impossible to get back, especially if the json response structure is a bit complicated. I was a bit in a hurry and lazy, so just prompted GPT to get me a script to call the api and store the response in a json file, but what happened was while returning the response from the stdout, the json string was encoded, and it became a mess to decode back. Always use requests or the native libraries in python. Do not rely on stdout responses, as it could be very different the way shells might interpret data from your native applications.

• There is no apparent way of restoring files of VS Code file explorer after deleting, like yeah CTRL + Z would work if you just deleted. But after a day, I realized I needed the files back, I tried to into `/tmp` folder, there were files I deleted earlier this week, but not from VS Code apparently. Really a bummer. Let me know if you know the place where VS Code stores deleted files, if it does.

Tech News

• Golang 1.23 released this week: https://tip.golang.org/doc/go1.23

  This looks like a big release with some alternate approaches getting added to the language, which are kind of double edged swords from most of the professionals opinion I noticed.

• X releases Grok AI 2: https://x.ai/blog/grok-2
  This actually caused some trend on twitter (ok X) of floods of images generated by Grok AI.

For more news, follow the Hackernewsletter:

https://mailchi.mp/hackernewsletter/712

That’s it from this week, I hope you did well this week, and have a happy week and weekend ahead!

Thank you for reading, let’s catch up in the next week.

Happy Coding :)

Thanks for reading Techstructive Weekly! Subscribe for free to receive new posts and support my work.