Skip to main content

Command Palette

Search for a command to run...

Coding isn't the most important skill as a SDE

Published
1 min read
Coding isn't the most important skill as a SDE
G

Hi, I'm Vikrant, a passionate software developer with a strong belief in the power of teamwork, empathy, and getting things done. With a background in building scalable and efficient backend systems, I've had the privilege of working with a range of technologies that excite me - from Express.js, Flask, and Django to React, PostGres, and MongoDB Atlas. My experience with Azure has given me a solid understanding of cloud infrastructure, and I've had a blast building and deploying applications that make a real impact. But what really gets me going is exploring the frontiers of AI and machine learning. I've had the opportunity to work on some amazing projects, including building advanced RAG applications, fine-tuning models like Phi2 on custom data, and even dabbling in web3 and Ethereum. For me, it's not just about writing code - it's about understanding the people and problems I'm trying to solve. I believe that empathy is the unsung hero of software development, and I strive to bring a human touch to everything I do. Whether it's collaborating with colleagues, communicating with clients, or simply trying to make sense of complex technical concepts, I'm always looking for ways to make technology more accessible and more meaningful. If you're looking for a team player who is passionate about building innovative solutions, let's connect! I'm always up for a chat about the latest tech trends, or just about life in general.

As naive i was as a developer with no professional experience as a engineer. I learned this thing while working with people from the industry

Coding isn't most important part

yes as a beginner you might think coding is what you do as developer. But the the truth is different. You have to first focus on understanding the business logic of the problem being solved. Then making a flow or laying down a approach about how you are going to do it. Then getting it reviewed by a senior or founder or a product manger and team. Then if you have made any mistakes in the flow, you will adapt take suggestions from the team. Then once you have good enough logic you have to decide a stack that is efficient in your use case and cost efficient. Then after all this you will start coding.