Let's not forget a lot of the technologies suck. Javascript makes my skin crawl.It's mostly horribly complicated and difficult because it's done primarily by amateurs who have no fucking idea what they're doing.
That is because you guys went herp derp into the angular camp.Haha WHAT? I'm sorry, client-side development is horribly complicated and difficult. I wish I could just do server-side development. That would be paradise.
I'm not a fan of the typed but not typed half assedness. Or that there are two equivalency operators. Or that there's all this shit built on top of it, forcing it to do stuff it wasn't meant for.Does JS make your skin crawl or do all the technologies/libraries built on top of it to help make it do shit it wasn't designed to do make your skin crawl?
Honestly, I don't know what better technology there is to use in our case. We need a complete framework plus widget library. We can't be selectively pulling random libraries out there to fulfill specific needs. We needed a complete, cohesive solution.That is because you guys went herp derp into the angular camp.
Or, in our case, using a technology that just came out of beta and was impossible to learn during that time because of constant breaking changes. Angular. That's the problem: NO ONE knows what they're doing. Other than, I suppose, the developers at Google (and even that's debatable).It's mostly horribly complicated and difficult because it's done primarily by amateurs who have no fucking idea what they're doing.
Honestly, I don't know what better technology there is to use in our case. We need a complete framework plus widget library. We can't be selectively pulling random libraries out there to fulfill specific needs. We needed a complete, cohesive solution.
Or, in our case, using a technology that just came out of beta and was impossible to learn during that time because of constant breaking changes. Angular. That's the problem: NO ONE knows what they're doing. Other than, I suppose, the developers at Google (and even that's debatable).
I don't mean knowing what you're doing technically; I mean knowing what you're doing regarding software design. Most front end guys have no idea why you'd have things like interface layers, why you wouldn't want to have business logic in a .js, etc... they mostly are not software developers and shouldn't be developing software.
I think most people here would agree web development is a highly saturated market which makes you easy to replace. When you're easy to replace it becomes much like an unskilled labor position and you have no real staying power unless you move up and out of that into something more specialized.
It's a fine way to cut your teeth and get into programming but most of us, especially those of us who work as developers, wouldn't recommend trying to make it into a career.
Well "web development" is a very ambiguous term though. If you plunk out HTML, CSS and some minimal JS to make a few things blink then yeah probably not career worthy.
Move south and work with me.Back on that job hunt, team. I wanted to be getting out of the govt at this point but I am looking at whatever, because I just can't keep doing this shit anymore. Oh well, at least it's the start of the fiscal year. Lots of people hiring, it seems.
What version of DOORs do you use? It's honestly not that bad -essentially fancy Excel.Believe me when I say it's worse than you could ever imagine