Ranter
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
Comments
-
BordedDev10511hAnd then you meet the dogmatic a-hole above you who says how things must be done while not having a clue.
Also, I wish my junior would do 0-5 more MFer will push such bad code sometimes because he's too lazy to fix it (and yes, I told him to fix it and why) -
retoor197910hI could make a list of using 3rd party source like frameworks. When you start, you make yourself because it's actually easier in someway than learn a while framework. Then you become medior and use a framework for everything you can imagine and writing stuff yourself is just crazy. When senior, if time is not a factor - you can write stuff yourself and the parts you need.
Nah, for business stuff using some existing components are still better for TTM. But privately you're able to make nice stuff yourself. -
atheist1005710h@retoor I miss working on a project where the library and framework were the product. Far more interesting than the bullshit I'm working on at the moment
-
retoor19799h@atheist I'm working on what I want now but I know what you mean. I did mainly fin tech. Data entry systems. Mainly web. Did so many years, tech changed a lot but still data entry systems. Also much stats what was nice. But now I can't see such system anymore.
-
Tounai14428hI skipped part of the 6-12 years, thanks to my low intelligence being unable to process “sophisticated” pieces of code.
A software developer's experience life cycle:
0 - 5 years: attempt to replicate what your current senior is preaching, assuming that's the right way. Reading "Clean code" and preach it as gospel, even though you don't practice any of it.
6-12 years: gained the belief that you are better off coming up with solutions yourself, usually "sophisticated" and "elegant" which to everyone else (and also yourself a few years later) is an over-complicated inheritance ridden shit show. You have realised the "Clean code" movement is actually a cult but still believe code reuse is the holy grail.
13+ years: finally realized that simplicity and pragmatism is the most sensible way for most software development. Code is now readable, maintainable and functional. You took the few good bits from "Clean code" and ignored the extremism. These are the golden years.
The problem is most developers jump ship and stop developing before reaching the golden years, thus resulting in most software projects looking like shit.
Unpopular opinion, but it doesn't make it untrue.
rant