if you are a curious engineer, it is so difficult not to have fomo.
every other domain seems interesting
every other book seems worth reading
every other problem seems worth solving
every other project looks like the next big thing
every other framework feels like something you should learn.
literally every single thing is a distraction. how do you even deal with that?
Projects are the best way to learn a programming language, and here are the three projects I did to learn Golang back in 2016.
1. Build a command-line todo application
2. Build a simple in-memory message broker
3. Chat Application using WebSockets
Each project covers a different aspect of Golang, and doing them all builds a holistic understanding. Here's what you will get from each project.
1. Build a command-line todo application
Golang is heavily used to build internal tools and command-line utilities. Building a todo application on the CLI will help you
- start with Go without being intimidated by the problem statement
- understand how to structure the code and follow best practices
2. Build a simple in-memory message broker
Message brokers are simple queues exposed over the network. Doing this project will help you understand
- writing HTTP web servers
- concurrency primitives like channels, mutexes, and WaitGroups
- goroutines as you will use them to simulate the load on this broker
3. Chat Application using WebSockets
Building a simple real-time chat application using WebSockets will help you understand
- how WebSockets and persistent connections work
- how to store and retrieve data from databases
Doing these projects well will cover most Golang constructs and help build a solid foundation to learn advanced topics.
Hope this helps.
When you join a new organization, it is quite natural to feel a strong urge to fix things. Let me ruffle some feathers here...
You will notice processes, tools, or practices that feel inefficient, outdated, or even wrong. Maybe the team uses Jira instead of Linear, Java instead of Go, MongoDB instead of MySQL (for a use case), or Tabs instead of Spaces. It will be tempting to point it all out immediately. Resist that urge.
Do not get overwhelmed by outrage. Every organization has quirks, and yours is no exception.
Complaining loudly in your early days won't make people rally behind you. You may be right, but what you lack is context. What looks foolish from the outside might have made perfect sense at the time.
So, start by asking why. Be curious. Ask questions, and listen closely. The more context you gather, the clearer the rationale will become.
At first, focus on integrating rather than fixing. Show reliability, do good work, and build relationships. Once you have established credibility, you'll find that people are more open to your perspective. That's when you can choose your battles carefully.
Keep this simple framework in mind:
- Ask why before suggesting what
- Listen more than you speak
- Build trust before pushing change
- Pick one thing, not everything
Prove your ideas with small wins, and show that you understand the context. Over time, you will gain the influence to bring major changes and improvements.
You can't fix everything on day one, but you can ruin trust in one.
Hope this helps.
@IRCTCofficial@RailMinIndia In the end had to pay 12 rs extra to choose a safer option called R-Wallet and there they are charging ~12rs extra so that payment gets safely debited. WOW.
It is not much of a big deal but how to claim the refund or your developers forget to build one???
Railone is such a shitty app made payment two times account got debited by a certain amount but on the app it shows transaction as failed.
On top of it there is no option to report or claim for a refund. these guys can’t even sort out such an basic and important feature. Shame