japherwocky
Joined 17 years ago
Joined 17 years ago
I'm sorry you work with incompetent people. Sounds like you're in a cubicle farm somewhere. While you're in a meeting swinging your seniority around, I'll be over here shipping products faster than your team.
It's really easy to work with. This is why people keep using it.
I like to see people push back on that; let's at least get to a state where we can consider dropping it from a project.
I'd also recommend tornadoweb.org - there are some nice demos included using moderately complex javascript in the browser and python on the server. I'm thinking in particular of the chat demo, which was invaluable for me in understanding how ajax apps work.
Really though, you need to just ship a few projects; the frustrations will clear up and you'll be more accurate in estimating how long things should take.
Some advice on turning this into a career: learning CSS and HTML is very useful, but there's (relatively) lots of jobs where you can program services for the backend and work with a frontend guy who's doing the design work and the user interface. Often for this sort of job though, the people hiring will ask you algorithm and data structure questions.
The other path you can take is really studying graphic design for a bit to train your artistic eye - if you can make pretty nice looking websites, and code up the backend to make them do interesting stuff, you're in a great position to go freelance / solo and build an app on the side.
And lastly, a third path: start writing a lot of javascript! It's getting used more and more, and a lot of the front end guys who "know javascript" are kind of shitty programmers, so there's a good pool of those sorts of jobs available.
Distributed teams are glorious when you weed out the jackasses. And in the meantime, remote guys are comfortable with much lower salary. That seems useful for a startup trying to keep costs down?