5 ms·

Some Russian people I know started a project that gives random obvious advice, along with a profanity to make you pay attention. Examples include: - change yo

by hkai 8y ago

Some Russian people I know started a project that gives random obvious advice, along with a profanity to make you pay attention. Examples include: - change your damn passwords! - reset the damn cache! - say no to your damn project manager! - use the damn frameworks! - stop creating the damn global variables! - don't use the damn "!important"! They've assembled a database of probably a few thousands of those wisdoms for different industries and it's truly entertaining. They've added an API too. Sadly it's not in English.

jimmaswell 8y ago
What's wrong with !important?
- coldtea 8y ago
  It's an exceptional bypass, so if you use it frequently, it means you didn't get the base class design right.
  - freehunter 8y ago
    Case in point, I extensively use !important in the very rare situation I'm doing front-end work, because I struggle immensely with CSS and can never seem to get it to render properly. And in almost every situation, !important leads to more problems than it solves. Yet I keep doing it, because I fundamentally don't understand CSS. If you use !important, you either understand CSS very well, or don't understand it at all.
    - exikyut 8y ago
      What would you say are the biggest pain points? Someone probably knows of a targeted resource or two that may help.
      - freehunter 8y ago
        I think honestly my biggest problem is just lack of familiarity. I don't do a lot of front-end work, and when I am doing front-end work it's probably a side project that I'm not getting paid for. If I'm working on my own time, the back-end stuff is more interesting to me so I spend as little time as possible on front-end. Order of precedence is the hardest thing for me to figure out, if I have three nested <div>s and a couple of <li> elements and all of them with a conflicting fontColor property, which one takes precedence? If I think really hard and trace back all the code, I can figure it out. Or I can put an !important on it and future me will deal with the consequences.
        bushin 8y ago
        Try BEM: http://getbem.com/naming/ http://getbem.com/naming/
        exikyut 8y ago
        I googled "css specificity" and it autocompleted "calculator", which led me to https://specificity.keegan.st/ https://specificity.keegan.st/. You can paste in a series of selectors (getting new boxes by clicking "duplicate"), then hit "Sort by specificity".
- lostcolony 8y ago
  Succinct but pretty thorough - https://j11y.io/css/dont-use-important/ https://j11y.io/css/dont-use-important/
tikhonj 8y ago
Do you have a link to it for the Russians in the audience?
- hkai 8y ago
  Fucking-great-advice.ru
amykyta 8y ago
Is it publicly available? Can you please share it?

by hkai 8y ago

jimmaswell 8y ago

What's wrong with !important?

coldtea 8y ago
It's an exceptional bypass, so if you use it frequently, it means you didn't get the base class design right.
- freehunter 8y ago
  Case in point, I extensively use !important in the very rare situation I'm doing front-end work, because I struggle immensely with CSS and can never seem to get it to render properly. And in almost every situation, !important leads to more problems than it solves. Yet I keep doing it, because I fundamentally don't understand CSS. If you use !important, you either understand CSS very well, or don't understand it at all.
  - exikyut 8y ago
    What would you say are the biggest pain points? Someone probably knows of a targeted resource or two that may help.
    - freehunter 8y ago
      I think honestly my biggest problem is just lack of familiarity. I don't do a lot of front-end work, and when I am doing front-end work it's probably a side project that I'm not getting paid for. If I'm working on my own time, the back-end stuff is more interesting to me so I spend as little time as possible on front-end. Order of precedence is the hardest thing for me to figure out, if I have three nested <div>s and a couple of <li> elements and all of them with a conflicting fontColor property, which one takes precedence? If I think really hard and trace back all the code, I can figure it out. Or I can put an !important on it and future me will deal with the consequences.
      - bushin 8y ago
        Try BEM: http://getbem.com/naming/ http://getbem.com/naming/
      - exikyut 8y ago
        I googled "css specificity" and it autocompleted "calculator", which led me to https://specificity.keegan.st/ https://specificity.keegan.st/. You can paste in a series of selectors (getting new boxes by clicking "duplicate"), then hit "Sort by specificity".
lostcolony 8y ago
Succinct but pretty thorough - https://j11y.io/css/dont-use-important/ https://j11y.io/css/dont-use-important/

tikhonj 8y ago

Do you have a link to it for the Russians in the audience?

hkai 8y ago
Fucking-great-advice.ru

amykyta 8y ago

Is it publicly available? Can you please share it?