Software engineer, ready to take on any challenges.

Hi guys, as I mentioned in my previous post, I'm setting up a collection of scripts to semi-automatically set up a buttery smooth Windows PowerShell and WSL dev environment in the blink of an eye. Just today, I finished and cleaned up everything. Here are the links to my scripts and dotfiles together with documentation and cheatsheets: - Dotfiles Github repo: https://github.com/doanhtu07/my-terminal-dotfiles - Documentation is already included in the README.md files in the Github repo - Cheatsheets on Notion: https://tudope.notion.site/Cheatsheets-5315b36f45cd41ab899d8f4538bb0e1f?pvs=4 - [Bonus] VSCode+Vim keybindings/settings for MacOS and Windows: https://github.com/doanhtu07/vscode-vim-settings As of now, I have a full setup for both MacOS and Windows+WSL machines. Linux setup should be very similar to MacOS and WSL. If you find any errors/issues, please don't hesitate to let me know. Have fun coding! As an extra bonus, here is me running WSL 2 in my transparent Wezterm on Windows inspired by this video ( https://youtu.be/G0_wVLhI-Ds?si=wiDIJUCYAULjpG8W )

I've been a long-time Mac user until now. Just a few days ago, I got my first personal Windows laptop for gaming and programming, and I'm pretty excited about it. I'm currently setting up my development environment on Windows and have just finished porting my VSCode with Vim settings from macOS to Windows. Feel free to check it out here: https://github.com/doanhtu07/vscode-vim-settings . Please let me know if you have any cool suggestions through issues or PRs. I'm also planning to port my dotfiles from macOS to Windows soon. I'll use a mix of PowerShell and WSL: PowerShell is for Wezterm and other Windows apps, while WSL is for Neovim with Linux-native apps. I'll update here and on my LinkedIn as soon as I finish.

In my latest post, I shared a ROS 2 setup using Docker. If you encounter issues running NoVNC, don't worry - there are alternative GUI options for Docker. Several solutions are available for you to explore. Now, I'd like to introduce a new setup using a Virtual Machine instead of Docker. You might wonder why. While Docker is fast, flexible, and easy to configure, it does have some drawbacks. One significant challenge is setting up bridged networking mode, which is notoriously difficult in Docker due to the lack of community support and documentation. However, bridged networking is essential when connecting to a real Turtlebot4 discovery server (such as a Raspberry Pi). With a virtual machine, it's a breeze to choose the bridged networking option. You can still find the same repository here: https://github.com/doanhtu07/test-ros2-docker I've updated the README to direct users to the appropriate setup instructions. For the Virtual Machine setup, the repository supports both VMWare (Fusion + Workstation) and VirtualBox. If you're concerned about the complexity of setting up a VM, don't be - I use Vagrant, a tool similar to Docker Compose but designed for managing multiple virtual machines. With my configuration file, all you need to do is to run a single command vagrant up , and the entire VM environment will be ready for you. That said, while Vagrant is great, be aware that virtual machines can be quite slow when it comes to initializing and preparing dependencies for ROS 2 and Turtlebot 4. It took me around 9 to 10 minutes to install everything, which made the development cycle for the config file quite slow. Feel free to try it out and reach out if you run into any issues!