Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Your first project will forever be your worst. By definition. The most important thing is to learn from it - and seems like you did, a lot - and take it to the next level for next time.
That's how companies roll. Try to upsell the technical debt as much as you can. Maybe they'll allow you 5-10% of each sprint for it. -
When I first started at my company, my first project was to implement a forgotten password feature that sent verification emails.
It used PHP backend with a Vue front end and spanned no less than 4 repos. It was damn near impossible to work out what needed to go where because I needed to fully understand how they all worked in unison.
I thought I had it all working perfectly well and testing all passed but that missed a glaring mistake that meant most emails were never sent. Oh well, no-one used it and the product died through lack of funding.
My team and me nearly finished a big new feature for our website.
I am a junior dev and this was the first big thing I was in charge of and now that I see how it unfold I feel really bad.
It consists of php backend (integrated into a 20 years old monolith) and vue frontend (punctually jumpstarted by a clusterfuck of typescript files included into php rendered html) and especially the frontend part looks so bad.
Vue is relatively young in our project and almost nobody has a clue about it. I learned so much about vue in the process, but the result is a behemoth of awfulness that grew over several months.
I have a really strong desire rewrite the whole mess, but I will never be officially allowed because it works and practically all the flaws in our code base are subject to the classic
"well, someday, somebody probably has to do something about that, but for now let's start this shiny new feature"
So for now I think about doing it secretly and pass it to my buddy to review it. I guess chances are high that not even the colleagues in my team (apart from my buddy) are going to notice, since they aren't as interested into vue as I am and don't have the overview over this features code as I do, but on the other hand it feels like something I could get in trouble for and apart from the cursed code base my company is great.
Have you ever bin that disgusted by your own production code before it was even one year old?
rant
legacy from start