• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.

Frontend - all encompasing bordom

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

  • TwoWolves
    replied
    Originally posted by AtW View Post
    The most boring thread of year 2021?

    We have a whole new year to beat that...

    Leave a comment:


  • AtW
    replied
    The most boring thread of year 2021?

    Leave a comment:


  • NickFitz
    replied
    I got kind of shoved into the front end basket by chance when the industry started drawing the distinction in the mid-2000s - it just so happened that I was mainly doing that stuff at the time, and I thus ended up stuck with it for a while. I still think CSS is great, but it's sufficiently complex now with things like flexbox and grid that it needs to be regarded as a specialism in its own right. And the flood of JS developers who want to make everything an SPA but don't even know how to write semantic HTML makes a lot of things intolerable to work on.

    I've been mainly Python/Django, with front end stuff done as needed (and semantically marked-up, and without relying on JavaScript for things that can be done purely in HTML and CSS), for the past few years. The relief is tremendous

    Leave a comment:


  • vetran
    replied
    Originally posted by KentDogWalker View Post

    yeah I think its time to switch to that, mostly legacy , even 1-2 year codebases, are css nightmares
    Yep let someone else configure what colour 'blue' the customer wants its hard enough to get them to document their processes well enough let alone decide which babies blanket colour to match for the front end.

    Leave a comment:


  • KentDogWalker
    replied
    Originally posted by TwoWolves View Post
    This is why I only work with the "back-end".
    yeah I think its time to switch to that, mostly legacy , even 1-2 year codebases, are css nightmares

    Leave a comment:


  • TwoWolves
    replied
    This is why I only work with the "back-end".

    Leave a comment:


  • OwlHoot
    replied
    Originally posted by eek View Post

    css bugs are always trial and error to fix because the bug is often not where it seems to be - it's the div next door that is the issue.
    Tell me about it. I've worked with plenty of divs in my time, sometimes, as you say, at the next desk!

    Leave a comment:


  • vetran
    replied
    Originally posted by eek View Post

    css bugs are always trial and error to fix because the bug is often not where it seems to be - it's the div next door that is the issue.
    So script the validation?

    Leave a comment:


  • eek
    replied
    Originally posted by vetran View Post

    so lots of well paid niche work then. Can you script it? Find the bug signatures in the code & either highlight or replace. Do it in < 1/3 of the time but charge for full time.

    https://stackoverflow.com/questions/...ion-in-notepad

    if you do it more than once consider automating it. Better pay, better quality & better life!
    css bugs are always trial and error to fix because the bug is often not where it seems to be - it's the div next door that is the issue.

    Leave a comment:


  • vetran
    replied
    Originally posted by KentDogWalker View Post
    All I seem to do is fix css bugs on tech debt, on 60% of clients
    so lots of well paid niche work then. Can you script it? Find the bug signatures in the code & either highlight or replace. Do it in < 1/3 of the time but charge for full time.

    https://stackoverflow.com/questions/...ion-in-notepad

    if you do it more than once consider automating it. Better pay, better quality & better life!
    Last edited by vetran; 30 December 2021, 13:15.

    Leave a comment:

Working...
X