Shame.css • Hacker News Board

Re: Shame.css

#31

Post by minikomi » Thu, Apr 25, 2013, 10:27 AM UTC

randall wrote: post #17

We have the same thing in Javascript, we call it 'hacks.js'. That's the place you go when things are broken and you're not yet ready to pay down tech debt. Hacks.css sounds nicer than shame.

I'd go with dirtyha.css

Re: Shame.css

#32

Post by benhowdle89 » Thu, Apr 25, 2013, 11:36 AM UTC

I do this, although I just call it `style.css`

Re: Shame.css

#33

Post by glitchdout » Thu, Apr 25, 2013, 11:42 AM UTC

tlrobinson wrote: post #29

Unfortunately I think most of my CSS would deserve to be in shame.css Related: is there a good short "remedial CSS for programmers" book or something?

I'm just going to leave here some of my CSS Good Practices bookmarks:

* https://github.com/necolas/idiomatic-css

* http://coding.smashingmagazine.com/2009/04/08/from-table-hel...

* http://engineering.appfolio.com/2012/11/16/css-architecture/

* http://www.stubbornella.org/content/2011/04/28/our-best-prac...

Re: Shame.css

#34

Post by swah » Thu, Apr 25, 2013, 11:45 AM UTC

nostrademons wrote: post #9

Pedantry: can we call it "guilt.css" instead? In psychological literature, guilt is defined as the "I did something bad" emotion, shame is the "I am bad" emotion. The crucial difference between them is that guilt can be fixed by making amends. That seems like exactly the mindset you want to encourage with this: guilt.css implies that you feel guilty about all the hacks you have and want to make amends, while shame.cs…

I understand it differently: they are ashamed of the code (its ugly), but not feeling guilty, since there are no alternatives at the moment...

Re: Shame.css

#35

Post by joetech » Thu, Apr 25, 2013, 12:18 PM UTC

Nice idea. Maybe we should use shame.php and shame.js as well.

Re: Shame.css

#36

Post by Pxtl » Thu, Apr 25, 2013, 12:29 PM UTC

Or you could just use a comment.

I know I can search my codebase for HACK and see all of my greatest embarrassments.

Re: Shame.css

#37

Post by spacec0wb0y » Thu, Apr 25, 2013, 1:07 PM UTC

My favourite thing about this, that they used a colour called #BADA55

Re: Shame.css

#38

Post by bjhoops1 » Thu, Apr 25, 2013, 1:39 PM UTC

This is a great idea. Too bad code can't really be isolated this way. I feel that marking a hack is one of the few legitimate uses for comments in code:

//TODO HACK HACK HACKITY HACK

Re: Shame.css

#39

Post by artursapek » Thu, Apr 25, 2013, 1:46 PM UTC

bjhoops1 wrote: post #38

This is a great idea. Too bad code can't really be isolated this way. I feel that marking a hack is one of the few legitimate uses for comments in code: //TODO HACK HACK HACKITY HACK

few legitimate uses for comments in code

You mean comments in CSS specifically?

Re: Shame.css

#40

Post by talmand » Thu, Apr 25, 2013, 2:08 PM UTC

hendrik-xdest wrote: post #18

Been doing this for years. I usually call the file ie8.css, though.

You're lucky, I've been having to increase the shame by having an ie7.css as well.