My VSCode configuration for 2024

Antonio Obradović — Tue, 23 Jan 2024 17:04:38 +0000

After a year of looking at the default GitHub VSCode theme I had enough and decided to finally customize it to my liking. I was tired of looking at the same ugly font and colors and started exploring for some VSCode setups.

Whilst exploring i stumbled upon a blog post by nexxel.dev where he talked about why he switched from Neovim back to VSCode and there I saw a screenshot of his configuration and wanted the same for myself. Thankfully he provided his whole configuration for VSCode and Neovim on his GitHub. I've been using his configuration for about 2 months, and decided to customize it a bit more to my liking.

Main changes I made to my configuration

The biggest thing that makes my configuration pop is font size and line height. I bumped them up quite a bit to get to my preferred sizes. With that VSCode already looks much better and with the addition of Dank Mono font it makes it complete. For the theme I use Tokyo Storm Gogh.

You can find my full configuration on my GitHub and for all developers I recommend having a repository like this to have your configuration in one place if you ever need it, or can't login to your vscode on your job like me.

Zen Mode

Possibly the best thing about VSCode for me is the zen mode. It allows me to have my file in the middle without any clutter, just my file, line numbers and that's it, if I need anything else I just shortcut my way to it. To enable zen mode you can either go to View > Appearance > Zen Mode or use the shortcut Ctrl + K Z.

Zen mode

What about Neovim?

I've been watching a lot of devaslife lately and seeing him code using Neovim has certainly made me want to try it, but I really like my VSCode configuration and feel very comfortable using it, although I do plan to try it in some distant future and possibly stick to it and replace VSCode for good.

Conclusion

I recommend to everybody to not just change your VSCode theme, but to edit and customize more, to find something to your liking and something you like to look at, because if you are like me you are looking at that VSCode editor for 8 hours every single day, so make it pretty.

This article was originally posted on my personal blog blog.obradovic.dev.

Development of the new Code Repo version

Antonio Obradović — Fri, 12 Jan 2024 21:09:46 +0000

The development of the new Code Repo version began about three weeks ago. Despite the holiday season with Christmas and New Year approaching, a significant amount of progress has been made, and the new version is already in good shape.

New tech stack

In the spirit of exploration, I decided to venture into new technologies. For the frontend, I initially opted for Astro, a static site generator that I've been eager to try for a while. Unfortunately, my experience with Astro wasn't as smooth as expected. After struggling with user authentication implementation, I decided to switch back to Next.js. The intricacies of Astro, particularly with its use of nanostores and islands, was a bit too much for me and decided to go back to my comfort zone. Nevertheless, I plan to revisit Astro in the future, hoping for a better understanding.

After a year of primarily working as a frontend developer, I aimed to return to backend development and finally embraced learning Go. Utilizing Fiber as the web framework with GORM, I found it to be a delightful stack, especially due to Fiber's resemblance to Express.js, a framework I've used in the past. Additionally, I integrated Supabase as the database. You might wonder why not use Supabase without Go and Fiber? Well, I wanted to learn Go and leverage Supabase, so I decided to combine the two.

Current progress

The upcoming Code Repo version will feature sign-in and sign-up functionality. Users can save their preferred templates and resources for future use and explore a handy playground feature for code testing and output visualization.

Sign in page of the new Code Repo version.

Most of the development time was invested in creating backend functionality for sign-in and sign-up, including models, routes, and controllers. Working with Go and Fiber posed its challenges, but with the combined efforts ChatGPT and me, we navigated through them successfully.

The frontend is still in its early stages, focusing primarily on login and signup pages and establishing user authentication. To achieve this, I utilized NextAuth.js, employing credentials provider and integrating it with my Go backend.

User authentication
Supabase integration with Go
Configuration of models, routes, and controllers for the backend
Addition of guide models and routes
Addition of resource models and routes

What's Next?

The next steps involve empowering administrators to create resources and guides. Subsequently, we'll fetch all resources and guides and display them on the frontend. Following that, users will gain the ability to save their preferred resources and guides for future reference.

You can also star the project on GitHub and look through the code. If you find any bugs or have any suggestions, feel free to open an issue or a pull request.

This article was originally posted on my personal blog blog.obradovic.dev.

Forem: Antonio Obradović