Describe your worst experience rather it is personal or professional as a developer/engineer. Maybe you were fixing a bug and something else crashes with no answers from Stacked Overflow to how to solve it.
I will start. I was fresh out of coding boot camp with my school project I have spent two weeks making that was ready to show employers. After I graduated, I forked my project to my GitHub and worked a minor bug on my server. After I deployed the site, the whole site crashed. I probably have spent a week trying to find out what went wrong before I gave up and decided to make a new web application to showcase other employers.
Have you been into a similar situation before? Maybe this will help others that might feel stressed out and alone or simply a good laugh while screaming, "Yep....been there before!".
Top comments (15)
I was just learning programming. I wrote a line of code(can't remember what) but I know I forgot to put the semi-colon. I spent 1 hour debugging the code. I hadn't learnt how to debug so I just kept scanning the code with me eyes. Really stressful.
Yep! Definitely been there! As far as semi-colons go, I have been pretty spoiled with using Prettier extension. A little bit afraid of if an employer doesn't want me to use VS Code as text editor🤐
You can always install prettier locally in your package, and then write a script to format your code. prettier.io/
My favorite tool other than kite!
An employer should never limit the tools a dev wants to use.
Very true!
The managers pushing the launch of the product for way too long, not understanding the impact of a bug and it's resolution, making each minor bug to feel like a mountain over our heads and changing designs multiple designs, before launch! Oh god, they feel like the only changes we need to do in a design change is changing hex codes in our code 🙄
"I am sure that is easy to do right?"
Hahaha exactly 😅
Tried building a website with my younger brother. He didn't like me using React or TailwindCSS in our project. He said that "I shouldn't use something that he doesn't understand". Is that something that I have to keep in mind when I start working professionally.
As my instructor puts it when I asked the same question to him about other devs using "var" instead of "let" or "const", "When in Rome, live like the Romans." Unfortunately, when you work with others, you have to adapt to how they run their code base especially early on as a junior dev(might be a different story when you are a senior).
However, when it comes to personal projects, I understand you are working with your brother, but unfortunately, you two would either need to agree on the technology to use and master it for the project or find other options for the project such as new partners aligned with your skills or working on the project yourself.
I will say that it is very cool that you have a brother that share the same interest as you! I came from a family that likes to farm and although I still enjoy it, I found my purpose outside of it vs my younger brother that couldn't tell you how to log "hello world". He is currently in college for agricultural management, so there are times we teach each other something new.
I'll keep that in mind.
Supporting IE11 is probably the worst experience that I ever had, professionally. I once broke prod because I used an arrow function in one of the decision branch of a feature. I can't even use webpack/babel/transpilers to help me out. I feel like I lost years of my life working in that setting.
I slowly been learning to adapt but sadly know the feeling
I was in a company full of senior developers that grew within the company when it was still a very small startup, with the same mentality of freelancers who start on their own with nobody around checking their code. Which means that the whole codebase was maintained by senior, but still written when they were very unexperienced with very poor standards. Most of them grew as seniors without looking around them, ignoring all the good bad practices. It was sort of like if you were around bad seniors who grew astray to make it short.
I was a junior and I once had a debate with a senior who wanted to change my way of coding, because in his opinion it was bad to adopt MVC. He wanted me to make a class which was a view, containing all the logics and all what should be in the model and view controller class too. Imagine something like a list element, which should contain only the UI code, containing also the logics to populate the list element, give a title to itself, monitor and react to any event that change the value of the list element (which was a switch), and change the data model according to this event. Something like a very specific 'settings switch cell' which was also able to switch and sync with the setting. Basically he wanted me to write all the logics inside that cell (or list element if we can call it like this).
I had to suck it up. Not only he was closed minded and he didn't even want to discuss it, and thought that his seniority gave him special rights, but after discussing with him I had negative remarks from my manager. Lesson learnt: the company was just falsely claiming to be non-hierarchical. In truth it had a strong hierarchical structure that put juniors into the position of having to do whatever seniors told them without questioning it.