Skip to main content

Command Palette

Search for a command to run...

What I learned working in a Startup?

Updated
0 min read
What I learned working in a Startup?
S

I am a Full stack developer who is obsessed with React, I like to explore cloud technologies like AWS and use the services to create various apps as hobby projects.

Hello Everyone,

My main purpose in writing this blog is to share my experience working in a startup. I have been working in this startup for over 5 months now. I am a Front End Engineer working with React.

Before I joined work I was unemployed for over 2 years and was eagerly searching for a job. During that time I tried a lot of options and nothing positive happened. So this is the first company I am working in and I feel really excited to tell you a lot about my experiences. This is also my first blog so forgive me if I make mistakes.

Every company has its own culture and its own lively workplace. My company has a very cool workplace, where there is a lot of communication between my peers and it feels really good. Everyone is super helpful and have a positive approach to everything. Solving issues becomes really simple when there are people around to help you or guide you. Weekly meeting and stand-ups are very common at our office. I opted to work from home and this is a new trend that can change the way a company can work.

I recently read that working from home has become very popular, many companies don't have an office, all of these work remotely. The employee has the freedom to work from where they want. Technically, I was not good with programming in React when I joined this company. I knew the basic flow of a React App, its Lifecycle methods, etc. But I had a bird's eye view of it.

During the first month of working with this company, I was asked to solve small logical or UI bugs. I was also asked to study the architecture of the app that was already built by someone else.

In the Second month, I totally got a deeper understanding of the whole app, I could find out and solve issues much faster and get to efficient solutions. I was given full support from the backend team and it was really amazing to know how teamwork could be so powerful.

During the 3rd and 4th Months, I was solving major bugs and issues, basically was to update the version of the app. The initial version was good, but had a lot of issues and had been visually updated to a V2. Creating something new is better than maintaining or updating the same thing. It takes a lot of time and patience to fix things together and prevent other things from falling apart. These 2 months were the most excellent and super productive months. It brought in a lot of challenges. Some of the challenges were to implement infinite scrolling for both tables and grid type information. It took me a lot of time to figure out and it was frustrating at the same time it was intriguing to solve and was really fun.

Everyone who works in any job will be able to work at his full potential when they enjoy the work that they do.

Passion to work is what drives you closer to your goals.

T
Todd7y ago

Which parts of the job are frustrating to you? Meaning, when you became frustrated, what was the "source" of the frustration? What parts of the coding did you enjoy vs the parts which were frustrating? I'm talking about at a high-level here e.g. "Learning the ins and outs of the libraries/framework was frustrating, solving logic bugs was fun..." etc...

S

Which parts of the job are frustrating to you?
I come up with a solution of a problem spending my whole energy and when I run it it doesn't work. If it doesn't work the first time then I can learn but if I spend over 2 weeks on it. I get really frustrated to work on it.

What parts of the coding did you enjoy vs the parts which were frustrating? It's pretty much the same as what you gave as an example. It was frustrating to see my code not working. But when it was finally successful I felt really happy.