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
-
As a senior, and an architect in my company, i'd like to also make you sse the big picture (and perhaps you already do). Sometimes adding a cool/new feature to some old/not cleaned code/undocumented /heavy coupled product can have some unseen/unexpected issues. And as seniors is our job to see that.... and to blame a junior if we didn't :D
-
If a junior came up and asked me that about one of our sites I'd probably rage and tell them off for not doing something productive.
If it's not broken and doesn't need the change then don't bother. Like you're literally wasting company time on useless crap that'll probably end up costing you more time in bugs.
Also if they're using jQuery 1.2 chances are you'll need a big re-write of all the jQuery code, so much time wasted.
If a sites that old though, I'd be telling the person it's time for a rebuild -
@jotamontecino @divil @fSociety
I wouldn't bring up old projects (learned that lesson when I first started as a fresh grad) the project that I'm working on with that senior is a fresh build that's why I was feeling uncomfortable working with him because he's used to build in a certain way that can be improved if he would explore other options, my main issue is that front end development is my domain and I feel he's more of a backend developer and when ever I bring up front end issues either regarding css or js he makes me feel that I'm being silly and front end stuff are just visuals and not relevant to his "real work" -
Then it's not because he is a senior... It's because he's lazy... and/or a prick...
Or already worked with a junior who suggested to use an unknown tech to him, and then he had to make sure and polish some product with an unknown tech.
And : if you build it, you run it....
But if it's jquery 1.2+... he's really lazy... -
@fSociety If that's the case, then the senior should articulate the reasons why the suggested change is not viable instead of accusing of acting out of place. Raging and shunning the junior's suggestions every time they don't fit the status quo will only squander their pro activeness.
-
@NeatNerdPrime you are correct in my junior view off things. But at my job and the website that I make, there is no room for unit test nor money
-
@NeatNerdPrime. We always try to get ourselves more time to do proper testing and QA, but usually we don't have enough time because most websites aren't expensive enough to cover the high development and testing process.
When we have clients paying us for premium we do more through testing before the product makes it to the client.
Found something true as 1 == 1
Life when you didn't know about browsers developer tools
Dear senior developer with xx years of development experience, please, I BEG OF YOU hear my humble unprofessional opinion.
Not every junior is a inexperienced low life.
Even though I'm glad that I'm working with someone of your wide skill set and expertise, I'm not working with you by choice nor it is my intention to distract or "steal" your knowledge.
When I suggested using a newer version of jQuery for this new project that didn't mean I'm challenging you to work on something new for your domain, I'm merely suggesting this change because jQuery 1.2 is just old and a big portion of it is deprecated.
When I suggest some changes on your CSS selectors that doesn't mean I'm acting out of place, it is my genuine interest of having effecient css where possible.
I know you (in your opinion) are the best full stack developer in the industry, but maaaan you kill me when you use js and regex to validate input type=email (table filp) ... Haalllloooo it's 2017 this Sunday aren't we supposed to progress instead of remaining in the same old same ?
RANT!!!
undefined
web
seniors
egotistical