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
-
@BordedDev It was a spreadsheet.
I'm fairly certain I used the standard saturated yellow from the color picker as the background color + black font.
/* As opposed to 'default' font color. */
So I'm fairly certain it was readable. -
@D-4got10-01 Ah yeah that would be perfectly readable
-
@jestdotty !sure whether I actually said the words, but yeah - that it was definitely a thought I had at the time.
'Dude, you don't like the aesthetics, just do it yourself.'
It's fucked up how people want these all-in-one workers that do everything /* who don't really exist */ while also paying them scraps / for just one position. -
@retoor Yup! That's the sad truth.
Doing things above your responsibilities is rarely rewarded.
Love the site.
Simple, elegant, works fine.
That's all that matters. -
@retoor As long as you have someone who appreciates it. I do agree on the making sure they know what you did, the PM isn't going to notice the 10% performance increase, but the users will, and you don't want sales to claim it was their "special" idea.
@D-4got10-01 Isn't "full-stack" the worst paid category when it comes to salaries? (says the generalist dev) -
@retoor I've met plenty of "I just do backend" type people, they use some "magic" backend to frontend library - their code tends to look shit either way (and written in C# or Java. And HTML in the MBs). And the ones I've met can get really offended if you mention anything about frontend to them (especially big, firm ones). Frontend "only" people tend to be really flexible and wanting to know more about the backend.
It exists because of the start-up boom IMO and the afore mentioned people getting on their high-horses. -
@retoor Since you wrote it, you'll know how it works. These people definitely don't (they would barely touch LINQ)
-
@retoor Yeah, but at current company they don't really care.
They _say_ that they appreciate it, but then I get absolutely nothing for it.
So while I still do it, because I actually care about doing great job, no rewards for me.
I had that at my two previous jobs, though.
People knew I do great job, they respected it && would give me more leeway during work. -
@BordedDev Technically they _should_ be earning more.
Something might've changed, though.
That, or it is the usual case of employers just being their dick-selves, wanting people w/ knowledge to do _all_ the necessary work, but !compensating them accordingly.
Some time ago I had a brief period of time when I had no tasks.
In order to stay productive, while having a lot of free time on my hands, I had decided to create a documentation of a feature in our game that has slightly different implementations depending on the platform on which the game is running.
Once I was done w/ the documentation, I shared it w/ the lead.
His feedback was along the lines of:
'It's OK, but the color palette that you used could've been better.'
/* What I used was basic colors: feature is available = green; !available = gray; partial availability = yellow, etc. Simple, easily readable. */
So instead of 'Thanks for documenting this.' I hear 'You have poor design skills - you should've used company's theme'.
/* I'm guessing since the company's logo uses some fancy colors, in lead's mind, those colors should've been used in documentation. */
Well, duh - I'm !a graphics artist / designer, so no shit.
There will definitely be no graphical fireworks in my documentation.
I fucking love working w/ people who have their priorities straight - '_fuck_ usefulness && correctness of data; It must be pretty too!'.
rant
priorities
bad leadership
pretty vs useful