Learn More
Resend Email
6
D-4got10-01
2d

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
Favorite
Ranter
Comments
  • 2
    2d
    That sounds like ass, with my current position I'd get praised to the high heavens for that kind of documentation. The only thing I disagree with is that yellow is readable (on a white background)
  • 2
    2d
    @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.
  • 2
    2d
    @D-4got10-01 Ah yeah that would be perfectly readable
  • 3
    1d
    I would've asked him to fix up the colors then
  • 2
    1d
    That's the problem if you do something extra - it can contain stuff that people don't like while they else wouldn't even complained at all. Indeed, instead of a thank you, you get shit :P Dammit :P

    Fuck design. I wish that everything looked like this: https://www.stroustrup.com/. It's responsive and fast! Performs perfect in google. <body bgcolor="FFFBFB"> for the win! He has only one part CSS and that's the only part not working so fine on mobile. The top header. I think my point is clear :P
  • 2
    1d
    @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.
  • 2
    1d
    @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.
  • 2
    1d
    @D-4got10-01 exactly, rarely, but sometimes very much. By always doing the extra mile I normally have a lot of freedom within companies to prioritize what I want and stuff. I'm a mayor flexer - my effort is not unnoticed. Not for the sake of it, but still you have to throw it people in their face if you did awesome stuff because many people don't care enough to notice it. Afaik you're one doing the extra mile also with your nice test setup & stuff.
  • 2
    1d
    @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)
  • 3
    1d
    @BordedDev kinda depends if you work with WordPress or build mission critical web applications tho regarding salary. So funny, back in the days everyone was a full stack dev. How could that ever become a new position like smth special. If you could do literally only one of the two I wonder how that's learned. You can't learn building a backend without never touched frontend at all.
  • 2
    1d
    @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.
  • 2
    1d
    @BordedDev haha, you're describing exactly me, I'm doing the backend to frontend thing 😁
  • 1
    1d
    @retoor Since you wrote it, you'll know how it works. These people definitely don't (they would barely touch LINQ)
  • 2
    1d
    @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.
  • 2
    1d
    @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.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment