Yogesh Devkate

@abolorreeeee Hey please do check ur dm need some guidance

I see contabo 1 year pricing my heart do gbim 😹 I can only afford 6 months for now

Hey guys How did u start building projects? How did u guys start initially? Watched tutorials n then rebuilt from the memory and add some features first build few projects like this and then try to build urself ! What u do ? Please drop ur path

@Tanishqstwt Hey please do check ur dm

you just need this two mf to start your go journey, after this just hop onto projects and build your way. even today i turn back to effective go for some concepts.

@codersGyan Okay Approximately how much time it will take. Rn i am learning the backend engineering in golang .

@DevkateYog2802 8 videos left to record. Total videos will be 22-25

Small thing that saves you in Go: DTOs. Whenever we pass data from one layer to another, across those network boundaries, we reach for a struct to decode or encode it. And here's where many of you make one quiet mistake. You reuse the entity struct for it. I've seen it happen. Suddenly fields you never wanted public are sitting right there in the response. A DTO fixes this. It's just another struct, holding only the fields you actually want to expose. Nothing more. Working on a YouTube series on this. Dropping soon.

@codersGyan sir anxiously waiting for this series ! when its coming please tell .

Dropping the full series on my YouTube. Subscribe so you don't miss it: @CodersGyan" target="_blank" rel="nofollow noopener">youtube.com/@CodersGyan

@codersGyan Sir please please 🙏 atleast tell thdate launch it soon

the full production Go backend series is coming here soon: @CodersGyan" target="_blank" rel="nofollow noopener">youtube.com/@CodersGyan

For the longest time I could never remember Go's log levels. Which one is more severe? What actually gets printed? So I sat down today and drew it. Debug is -4, Info is 0, Warn is 4, Error is 8. Once I saw them on a scale, it just clicked. Set your logger to Info and it prints Info and everything above it. Warn and Error included. Anything below, like Debug, stays quiet. That's the whole rule. Current level and greater. I used to dread this. Now I just remember the picture. If something looks confusing to you too, don't take any tension... This one's going into the production Go backend series I'm dropping soon.

@21prnv Tmkoc is permanent ♾️

We cooking again

Day 1 building project in golang. -understood how the http server works internally. -how backend , frontend, database is connected to each other and also understand what happens when client send a request. -got to know about the postman and what it is used for. #golang #go

Finally 😃 After a lot of confusion and brainstorming Today I started Building my Project in golang . Honestly ,today I am actually feel like I have made some progress. #buildinpublic

@buildwithyash Hey brother please do check ur dm need guidance

Forgot to Update you all last week i got an founding engineer/full stack role at startup . Have received some money in advanced itself . Currently developing a full platform for them lot of learning for me i have to see which stack to choice or which not everything in my hand. Monthly salary will cover my yearly college fee My cofounder is very sweet and one of the best client /person i have worked on till date

@codersGyan Sir kab aa raha hai date to bata do ?

Every Go tutorial ships a naked http.ListenAndServe and moves on. That server has no timeouts. None. Which means it's a Slowloris DoS waiting to happen. One slow client can just hold connections open and starve you. Three lines fix it. ReadTimeout, WriteTimeout, IdleTimeout. That's the difference between a toy server and a production one. And honestly? It's sad Go doesn't give you sensible defaults here. You have to know to add them.

@BhargavLearns bro how to start building project after watching this videos? i m really tired of watching videos i want to build ! where should i start and how ? please help

A lot of people ask for resources to learn Python, but honestly, no resource is suitable for everyone. So here I am, going to give you resources based on which level you are: Level 1 (Complete beginner): If you haven't studied Python ever in your life and you genuinely want to learn it, in-depth, to get a bulletproof understanding of fundamentals. I would recommend you all to study from the Code with Harry while following a book called "Learning Python by Mark Lutz You can basically give the book and the video as a source to notebookLm and then ask notebookLm to give you a study plan to cover both the parts simultaneously from the book as well as the tutorial. If you encounter something new in the book, try to learn it from the book or else go to YouTube and search for the topic. If you are not comfortable with Hindi, I prefer you watch Bro Code. If you can understand most parts of the book, then don't be ashamed to drop the tutorial and learn from the book all alone. While solving questions using GPT. Level 2 (intermediate level) If you have studied Python or have prior knowledge of programming, you can refer to Dave Ebbelaar's Python for AI while keeping the book "Learning Python by Mark Lutz as a reference. Keep one thing in mind: this combination will not provide you with questions to solve, so whenever you feel like you need to revise anything or solve more questions on any topic, go to GPT and ask for questions. Also, make sure you solve predict the outcome questions (tricky ones) as much as you can. Level 3 (advanced level) If you have worked with Python for a long time and just want to strengthen your fundamentals, or maybe give time to your fundamentals. Then you should only follow "Learning Python by Mark Lutz. Just pass this book as a source in a notebooklm, get quick summaries, important points, ask to give questions based on references, learn almost everything working under the hood, and that's it. Lastly, this is my personal combination,n which I recommend to anyone who is starting. However, one last thing to everyone, build to learn. Whenever you learn a topic, open the VC code and just solve questions.

I spent a lot of time looking for the right concept when I didn't fully understand the problem itself. Now I'll first explain the problem in simple words. Only then will I think about the solution. Understanding before coding. #golang #backend #buildinpublic

@codersGyan From now on,before solving any problem,I will first understand what problem I am actually solving.I will explain it on paper in the simplest way possible so that even a nontechnical person can understand it.Then I will identify the concepts needed to solve it and finally the code

Before I write a single line of code, I draw the whole thing out like this. For years I had the biggest problem so many of us have. I'd jump straight into the tech and the architecture before I actually understood the problem I was solving. And here's the honest part. Understanding the problem means you can explain and draw the feature for a non technical person. Most of us can't. We only talk tech language. I include myself in that. So now I do this first. User flow stories, mapped out as a flowchart. The same boring thing they taught us back in school. If you can't draw it clearly, you don't understand the problem yet. And if you don't understand the problem, no architecture is going to save you.

went for a walk this morning, no plan just went 3.85 km and some bodyweight exercises. Now starting with Golang . let's see how far I get today #golang #buildinpublic

@gummybearansh hey bro please check out ur dm need help

Project 02/15: Raw TCP HTTP Server. Bypassed net/http and built a concurrent web server over raw TCP sockets. Handled goroutine multiplexing, parsed HTTP/1.1 headers from scratch, and built an O(1) routing table. Link in comments.

@NitinthisSide_ please check ur dm need help

This weekend I decided to learn TypeScript but not by tutorials and actually build something with it. Built an AI Customer Support Agent using: • TypeScript • Node.js • Express • Sequelize • PostgreSQL • Gemini Features: → Persistent conversations → Session management → AI-powered responses → Company knowledge base → Error handling & validation → Production-ready architecture Still reviewing the codebase , but this weekend reminded me: The fastest way to learn a technology is to ship something real with it. Back to code reviews now.

Started learning Go through tutorials got distracted, nothing stuck. Switched it up: build first, hit a wall, then ask Google/GPT for a worked example + where it's used in real backend code. Finally understand structs, pointers, slices and enjoying the process now. #golang

@codersGyan okay sir

@DevkateYog2802 Currently recording. Update you soon.

Two weeks ago I changed how I post. Less polished. More of just what I actually did that day. What I built, what broke, what I learned, what I found useful. And the response went somewhere I did not expect. Hundreds of new followers and connections, plus reshares and saves. So many of you told me you like these new formats, and that means a lot. So I'm going to keep doing exactly this. The daily work, the wins and the mess. Lot more to learn and share. Stay tuned.