Week #29

It was a fun week. There was a bit of laziness, for sure, but also some work done. I didn’t create a video this week and took a bit of a break. I think it is as important to upskill as it is to maintain streaks of uploading.

Quote of the week

"The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn."
— Alvin Toffler

This hits well. With AI in town, AI will require you to learn the art of debugging, unlearn things like copy-pasting from the Internet, and change your perception of code and technology.

It will be less about learning, and more about re-learning or removing the perceptions about the already existing things while writing code. The technology is moving fast and with AI it will pick up pace like never before, code will be a mess, and codebases will be doomed, but someone with an open mindset, and a person who knows his craft will surely survive.

Read

  • ASDF has been re-written in Golang from BASH: This is nice, I also used to write a lot of bash scripts in my initial novice days, like downloading data, virtual environment management, utilities, etc. but over the years I moved from script kiddie to python and golang scripts, as I have more control and it works for a lot more edge cases then figuring out string parsing on bash.
  • How we replaced our react frontend with Golang and Webassembly: This is the second thing I am heard about Golang this week, moving from X to Golang in some way or the other. The adoption rate of Golang is high and it makes sense, it is a simple language. Simple to read and write, and the one that scales as well.
  • My writing process, and how I keep it sustainable:
    I am inspired by this article, the author claims to write everything in one go (not everything but the meat of the post) that is true for me. I just flush out my thoughts in one sitting too, however, my editing process is haywire, and haphazard. I usually don’t revise, I am not a professional technical writer, but when I do I do editing as they come.
  • A slow blogging year: Wow, I also need to do some posts this year, I moved from 41 (2021), 40 (2022), 11 (2023), and 14 (2024). Need to write more, On the initial day, I had too much to express, but as days progressed, the friction reduced but the quality of that increased, first, it was about quantity, the motivation, and then it was consistency about improving.

Watched

  • How (junior) developers are getting screwed:
    I agree with this point, AI is a double-edged sword. If used properly it is a weapon, but if used without knowing what it is doing, it would not help in the long run. But for junior developers, it is quite hard to figure out why without AI ,leave it aside with AI, it will be a new skill to add moving ahead in a few years. How to use AI effectively as a developer, previously which was searching, debugger, and documentation, next it will be one more tool in the toolbelt.Double click to interact with video

Learnt

  • Learnt about qute browser
    • Load and save sessions
    • Map keybindings from commands
  • Using request.arg.to_dict to get the query parameters as a dictionary of string with the list of values in Flask APIs

Tech News

  • Golang 1.24 released: I have created 3 videos about splitsequence, json omit tag, and weak package.
  • OpenAI roadmap: This is big, the GPT-5 will be the last model for GPT family, i.e. the next models will be thinking-based and not just predicting the next token-like models, I mean those will be token prediction only but the way the final token will come as final will be lot more nuanced and not silly. Instead of us prompting it again (this is wrong, what about this case??) it will think thoroughly and give the result.
  • GitHub Copilot language server

For more news, follow the Hackernewsletter and for software development/coding articles, join daily.dev.

Leave a comment

That’s it from this 29th edition of my weekly learning, I hope you enjoyed it, and leave comments on what you think about some of my takes or any feedback.

Thanks for reading Techstructive Weekly! This post is public so feel free to share it.

Share

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