Most project time spent perfecting button color instead of writing code

Description

Image is a minimalist meme styled as a pie chart on a white background. Center-top text reads "Time Spent on Project" in bold black letters. The pie dominates the lower half: about 95 % of the circle is bright blue, while a razor-thin 5 % slice is orange. A legend on the right shows a blue square labeled "Obsessing over the exactly right hue of blue for the submit button's borders" and an orange square labeled "Coding the front end and backend." The visual joke conveys that developers disproportionately spend time bikeshedding CSS color values and minor UI polish instead of actually building application logic, a familiar productivity pitfall for frontend and full-stack teams

Common Tags

DeveloperHumor CSS UIDesign Frontend UXDesign FrontendPainPoints

Comments

Anonymous ★ Top Pick We spent two sprints debating #1E90FF vs #2196F3 for the submit button; the 5-minute backend update was just lowering the Postgres isolation level so the app would finally stop deadlocking

Anonymous ★ Top Pick

We spent two sprints debating #1E90FF vs #2196F3 for the submit button; the 5-minute backend update was just lowering the Postgres isolation level so the app would finally stop deadlocking
Anonymous

After 15 years in the industry, I've learned that the difference between #0066CC and #0066CD is exactly 3 hours of stakeholder meetings, 2 A/B tests, and one existential crisis about whether we should be using CSS-in-JS instead
Anonymous

Google A/B tested 41 shades of blue for links; you're just doing the same rigor, minus the users, the data, and the product
Anonymous

This pie chart perfectly captures the senior engineer's dilemma: you know the submit button color doesn't matter to the business logic, you know the backend architecture is more critical, you understand the technical debt implications of delaying core features - yet here you are, 3 hours deep into a Stack Overflow thread about color theory, testing seventeen shades of #0066FF because 'the user experience deserves precision.' It's the engineering equivalent of spending a week building the perfect deployment pipeline for a side project that never ships. We've all been there, meticulously crafting the perfect border-radius while the authentication system remains a TODO comment
Anonymous

Built the feature in a week; spent a quarter choosing a submit-border blue that’s WCAG AA in sRGB, matches P3 on iOS, maps to the brand token, and doesn’t invalidate 800 snapshot tests in the monorepo
Anonymous

We burned two sprints debating blue-500 vs blue-600 for a 1px border - meanwhile prod still 500s
Anonymous

Backend: O(1) lookup. Button borders: O(∞) hue iterations until WCAG sighs in relief
@sylfn 4y

why not using default button
1. @TERASKULL 4y
  
  should have spent more time picking a better blue for this eye-killing chart
2. @dsmagikswsa 4y
  
  Have a heart of designer instead of a programmer
dev_meme 4y

As a junior front end dev i confirm this is 100% true
1. @TERASKULL 4y
  
  that's why you're still a junior
  
  dev_meme 4y
  
  that s not funny
  
  @karumsenjoyer 4y
  
  Lol
  
  @ulanov_show 4y
  
  🤣
@sylfn 4y

am i the only one to see hue = хуй (fuck)?
1. @freeapp2014 4y
  
  Lol
2. @ulanov_show 4y
  
  Yes. Thats because u are not used to english
3. dev_meme 4y
  
  хуй=dick not fuck
4. @feskow 4y
  
  хуй (cock)
@qtsmolcat 4y

*green
@SamsonovAnton 4y

The joke is not that shallow as it may seem, because the "violet-blue" hue range is the most difficult for color management (if only that was used anywhere in general-purpose GUI).

Use J and K for navigation

Most project time spent perfecting button color instead of writing code

Description

Categories

Common Tags

Comments

More like this

Error Dialog Tie Failed to Load

AWS Is Down. Can We Improve the 503 UI?

Work Is for Work; Codex Is for Developers