The best programmer is the one who's been through the most pain, discuss....
-
Whilst checking out MVC6 recently (which I think is brilliant and took no time to get up and running with) I had the misfortune to have to faff around with some CSS again. I rarely go near it and only have painful experiences of trying to do anything useful with it. Took about 3 hours to get my head around MVC6 and create a new site and about the same to try and solve (unsuccessfully) a single CSS issue. Am I right in thinking that to be good at CSS one of the main requirements is that you've been through the pain of solving a million different layout and browser problems?
-
Whilst checking out MVC6 recently (which I think is brilliant and took no time to get up and running with) I had the misfortune to have to faff around with some CSS again. I rarely go near it and only have painful experiences of trying to do anything useful with it. Took about 3 hours to get my head around MVC6 and create a new site and about the same to try and solve (unsuccessfully) a single CSS issue. Am I right in thinking that to be good at CSS one of the main requirements is that you've been through the pain of solving a million different layout and browser problems?
Google can be your friend. A List Apart: For People Who Make Websites[^] is a good resource for CSS.
Decrease the belief in God, and you increase the numbers of those who wish to play at being God by being “society’s supervisors,” who deny the existence of divine standards, but are very serious about imposing their own standards on society.-Neal A. Maxwell You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
-
Whilst checking out MVC6 recently (which I think is brilliant and took no time to get up and running with) I had the misfortune to have to faff around with some CSS again. I rarely go near it and only have painful experiences of trying to do anything useful with it. Took about 3 hours to get my head around MVC6 and create a new site and about the same to try and solve (unsuccessfully) a single CSS issue. Am I right in thinking that to be good at CSS one of the main requirements is that you've been through the pain of solving a million different layout and browser problems?
One problem with trying to find help with CSS problems is that there are sometimes a dozen different ways to achieve an effect/layout but not all methods work everywhere, and may break or be deprecated in the near future. Weeding through all the irrelevant stuff and trying different solutions makes you a better developer. :)
"Go forth into the source" - Neal Morse
-
Whilst checking out MVC6 recently (which I think is brilliant and took no time to get up and running with) I had the misfortune to have to faff around with some CSS again. I rarely go near it and only have painful experiences of trying to do anything useful with it. Took about 3 hours to get my head around MVC6 and create a new site and about the same to try and solve (unsuccessfully) a single CSS issue. Am I right in thinking that to be good at CSS one of the main requirements is that you've been through the pain of solving a million different layout and browser problems?
I was working for a company 15 years ago that cared mostly about how each of their websites looked as they saw it as the profit engine. They didn't care about coding standards or security, just look and feel. They wanted things to be laid out exactly to their specifications. I would sit for hours making little changes to my CSS and clicking refresh. I learned CSS that way and even with CSS 3, things have not changed much. CSS is worth learning because like SQL, it doesn't change much and once you learn it, you know it for life.
-
I was working for a company 15 years ago that cared mostly about how each of their websites looked as they saw it as the profit engine. They didn't care about coding standards or security, just look and feel. They wanted things to be laid out exactly to their specifications. I would sit for hours making little changes to my CSS and clicking refresh. I learned CSS that way and even with CSS 3, things have not changed much. CSS is worth learning because like SQL, it doesn't change much and once you learn it, you know it for life.
-
Whilst checking out MVC6 recently (which I think is brilliant and took no time to get up and running with) I had the misfortune to have to faff around with some CSS again. I rarely go near it and only have painful experiences of trying to do anything useful with it. Took about 3 hours to get my head around MVC6 and create a new site and about the same to try and solve (unsuccessfully) a single CSS issue. Am I right in thinking that to be good at CSS one of the main requirements is that you've been through the pain of solving a million different layout and browser problems?
With CSS, I think of it as stacks and boxes. If I add bizarre layouts with tables, I'm just begging for it. The box model in CSS (margin, border, padding, width) is what gets me. The key is to keep it simple. It's also mobile friendly too. :cool:
-
Whilst checking out MVC6 recently (which I think is brilliant and took no time to get up and running with) I had the misfortune to have to faff around with some CSS again. I rarely go near it and only have painful experiences of trying to do anything useful with it. Took about 3 hours to get my head around MVC6 and create a new site and about the same to try and solve (unsuccessfully) a single CSS issue. Am I right in thinking that to be good at CSS one of the main requirements is that you've been through the pain of solving a million different layout and browser problems?
I don't care what discipline, the old guy with the years on his face has seen it before.
-
Whilst checking out MVC6 recently (which I think is brilliant and took no time to get up and running with) I had the misfortune to have to faff around with some CSS again. I rarely go near it and only have painful experiences of trying to do anything useful with it. Took about 3 hours to get my head around MVC6 and create a new site and about the same to try and solve (unsuccessfully) a single CSS issue. Am I right in thinking that to be good at CSS one of the main requirements is that you've been through the pain of solving a million different layout and browser problems?
Having as a consultant tried to salvage two companies that had coded black holes inside their paper bags, and repeating the experience as an employee in a company managed by those that saw competence as a threat, I would have to agree that you learn a lot in suffering through the process of trying to save people from their mistakes. It's far more efficient than making all the mistakes yourself.