Earlier quoted context omitted.
Six figures? In the US? Sometimes I wonder why companies even pay developers so much in the US. I'm a specialised medical embedded software developer in the UK and I'm not even halfway to six figures, and will likely never hit it. It astounds me that companies don't hire twice as many non-US developers for the same price and get more work for their money. Note, I'm not talking about outsourcing to the absolute cheape…
The US salaries in IT are huge, but you need to take into account that they have to pay a lot to have a quality of life comparable to what a minimum wage worker is getting in west Europe. If you have a few kids, I would bet you are not that bad in UK with one fewer digit.
Things I wish I’d known about CSS
51–60 of 340 posts
Re: Things I wish I’d known about CSS
#52Yikes. I've been earning 6 figures as of about two years ago doing mostly HTML and CSS UI design for a bank. And I still did not know about many of these! I guess they are things I wish I'd known about CSS! Better late than never I guess.
I've done CSS since 1999, none of this was new to me, and I've never earned 6 figures for doing HTML and CSS. I moved my career away from HTML/CSS in order to earn more.
Re: Things I wish I’d known about CSS
#53If you're looking for world-class CSS knowledge, start with https://every-layout.dev ; if you build UI for a living and haven't encountered axiomatic css and layout primitives, they're likely to change your world.
Re: Things I wish I’d known about CSS
#54I think a better understanding between inline and block is, that inline-elements do not generate a block. The idea of a block breaks down for inline elements, especially when they go over multiple lines. It's not just a horizontal expansion. So understand what creating a block means. Inline-elements don't.
how does this help explain inline-block? your explanation must accommodate the holes.
Re: Things I wish I’d known about CSS
#55Re: Things I wish I’d known about CSS
#56Anybody knows a good book on CSS for ppl with a solid programming background? Every couple of years I try something and fail. Somehow the tutorial rave about the cascading on and on, and when it comes how to strategically design a good SAP working on different devices the stuff gets mute quickly.
Re: Things I wish I’d known about CSS
#57Yikes. I've been earning 6 figures as of about two years ago doing mostly HTML and CSS UI design for a bank. And I still did not know about many of these! I guess they are things I wish I'd known about CSS! Better late than never I guess.
Six figures? In the US? Sometimes I wonder why companies even pay developers so much in the US. I'm a specialised medical embedded software developer in the UK and I'm not even halfway to six figures, and will likely never hit it. It astounds me that companies don't hire twice as many non-US developers for the same price and get more work for their money. Note, I'm not talking about outsourcing to the absolute cheape…
At this point in my life you would have to pay me around six figures for me to do CSS seriously on a daily basis (and it’s likely I’ll still burn out and leave). The cross browser and device testing alone is so tedious and stress inducing that I simply won’t do the job below a certain price point (or I will out of desperation but definitely will bounce ASAP). The unsaid thing about doing heavy CSS work is that it doubles as a QA job from all the testing required.
And again, I’m someone that’s good at it. You can’t pay me enough to do it, not if I have choices.
Re: Things I wish I’d known about CSS
#58If you're looking for world-class CSS knowledge, start with https://every-layout.dev ; if you build UI for a living and haven't encountered axiomatic css and layout primitives, they're likely to change your world.
The ; in your link sends me to about:blank#blocked.
Re: Things I wish I’d known about CSS
#59I learned CSS over the years by gradually solving problems I encountered building apps. Compare this to people learning CSS now as evidenced by the #100DaysOfCode tag on Twitter. The learning technique is comprised primarily of using gradient-heavy, absolutely positioned HTML elements to create a photo-realistic, 3D rendering of objects.
The results are pretty amazing, but I have my doubts about whether these skills are easily translatable for building an interactive, responsive UI. Some examples:
https://twitter.com/bauervadim/status/1282264611912327169
https://twitter.com/mercyoncode/status/1282449080132804609
https://twitter.com/ellie_html/status/1276177277315932161
https://twitter.com/thecoffeejesus/status/128204582508278169...
Re: Things I wish I’d known about CSS
#60Anybody knows a good book on CSS for ppl with a solid programming background? Every couple of years I try something and fail. Somehow the tutorial rave about the cascading on and on, and when it comes how to strategically design a good SAP working on different devices the stuff gets mute quickly.
Can't recommend Andy Bell and Heydon Pickering's Everyday Layout enough. It's a wonderful resource for learning (and re-learning) contemporary best practice CSS. https://every-layout.dev/