What? You guys actually design!? And involve the lower-end guys on it!?
This is Computer Science [Software Engineering] we're talking, right? (Most companies I've applied with seem to either want coders
[i.e. cut-n-paste script monkeys] and/or have the cookie-cutter mentality [we need 2-5 years experience in the industry, with these tools/environment for this entry-level job].)
And these goobers wonder why they cannot get a real job outside the gaming/start-up industry? They have no respect for battle-tested processes that make money.
Well, to be fair the industry is kinda stupid: I was told by an interviewer that they wanted someone with more OOP experience
even though I've done Delphi, Ada 2005, some C#, and a touch of Java. [They wanted C#-experience, and so likely discounted all other experience I had with OOP.] — another thing that disturbs me about the industry is how many don't know the proper tools for the task (i.e. everything should be addressed with the C/C++/C# [or PHP if its web-based] hammer — even if it would be simple in something like LISP, or FORTH)*.
Honestly I am getting sick and tired of these entitled pansies... and they blame the boomers for their woes. I have not seen one “kid” under 28 or so that can code for sh_t. Outside iPhone apps, games, and social media BS stuff they have no concept of business software. They think that we will give them a one page document and check on them once a month while throwing money at them.
One page? I think I'd rather have a real specification than play the game of infinite tweaks and bug-fixes
— you can get seriously screwed if you have a different/lower rate for bug-fixes than new-features and the client slides what would be new features into the bug-fix requests. That simply doesn't happen with a proper specification: it is either conformant or non-conformant.
* List and stack-oriented languages force a different approach, one that is far more suitable for some types of problems than c-style languages, or even the procedural/imperative (or OOP) paradigms.
No cut and paste here. We are not bleeding edge, but we do want all new code to be vetted through some sort of design so we avoid building layers of unmaintainable junk that you can never get rid of without bringing the system down.
We have an internet app but our revenue maker is a client/server database app that actually has to be installed. The web apps I am currently proposing a redesign, they were made with too much code in the UI. Internet apps (desktops too) need to have a stupid as possible UI layer that only handles rendering nothing else. My predecessor lead a design that put too much business logic in the web layer and it really sucks.