Slashdot Mirror


Web Development - A Tough Job to Have?

frank_tudor asks: "Hey everyone, I have been a web developer for seven years now. I have had some moments of success, but mostly down moments with low pay, less than stable work, and unemployment. I love what I do and I don't mind the trends and technology changes that come with web development, but I am getting older and have been mulling a change in professions. But to what? I an wondering what those of you on Slashdot think about web development as a job, and what professions they think would be both stable and challenging to consider?"

30 of 112 comments (clear)

  1. As a Web Developer ... by eldavojohn · · Score: 5, Insightful
    I've been developing web apps for two years in a Fortune 500 company. I've run the gambit. ASPs, JSPs, Weblogic, Websphere, Plum Tree, Axis, Spring/Struts, etc. Let me point out the my easily identified cons of web development:
    • The technology & framework you're using will be obsolete in two months (see above list).
    • Your scope creep is worse than another project because web technologies (like Web 2.0) are constantly offering new features. The customer sees them and wants them ... now.
    • A lot of times, you can add something graphical in two minutes and the customer might wet themselves when they see it. On the other hand, you can spend two months knocking out major requirements in back-end functionality and the customer will probably ask you why they're paying you since nothing's changed in the interface.
    • You need GUI experience and a sort of artistic knack (or at least a team member with this expertise).
    • You need a solid programming background for functionality (or at least a team member with this expertise).
    • You need to know a lot about security (or at least a team member with this expertise).
    • You need to know a lot about databases (or at least a team member with this expertise).
    • If you rely on team members for the above, you need to keep constant communication with them through every step of the development process--this is why it's often better for you to just learn everything.
    • You have to develop original content for the website. Seriously, where do people get their pictures for websites? I want licensed images of people standing around and using computers in my website ... I had better get my digital camera and waver forms and hit the office cubicles.
    • A lot of the tools are FOSS. My company's FOSS Process has 20-25 control gates. Most of them are lawyers.
    • You sometimes have to deal with lawyers.
    • It's a tiered or layered framework that you work with & therefore to introduce a new functionality, it has to be implemented from front to back. This means that it's fairly difficult to have people in charge of a layer (like presentation-side versus functional server-side versus database) because they all have to play ball in order to get the functionality working.
    • You have to balance server load with what can safely be done on the client side.
    Now, I know a lot of the above elements are present in other programming/IT jobs but I do find web development to be the most difficult form of programming.

    The pros of web development:
    • A lot of jobs are available.
    • The pay is decent.
    It doesn't sound very fun & yet I still continue to do it. If you want a suggestion, only take web development jobs on a large team that already experiences success. Learn how to fit in and then you can work on taking on challenging tasks. As you can see from above, I'm expected to do it all and then some. I've been forced to do things as a one man team and I don't like it. Don't enter into anything unless your duties are well defined and involve well built products, tools & technologies.

    Most importantly, educate yourself about enhancements, advancements & changes and stay well rounded. Best thing I ever did was set up an Apache Tomcat server at my home and start tinkering around. Well, I suppose that's another story though ...
    --
    My work here is dung.
    1. Re:As a Web Developer ... by after+fallout · · Score: 2, Insightful

      You can layer it out a little (one person in charge of database, one in charge of stylesheets/user-interface, everyone else does everything else).

      Communication is key though, we spend more time talking about what we are doing than actually doing it. Also, a very strong change management procedure helps.

    2. Re:As a Web Developer ... by Anonymous Coward · · Score: 2, Interesting

      "A lot of times, you can add something graphical in two minutes and the customer might wet themselves when they see it. On the other hand, you can spend two months knocking out major requirements in back-end functionality and the customer will probably ask you why they're paying you since nothing's changed in the interface."

      Amen to that brother.

      I just had the same experience again the other day. The "CEO" turns to me and says, "So for tha past week you've only worked on the login page?"

      I just wanted to scream him down.

    3. Re:As a Web Developer ... by suv4x4 · · Score: 5, Insightful

      "A lot of times, you can add something graphical in two minutes and the customer might wet themselves when they see it. On the other hand, you can spend two months knocking out major requirements in back-end functionality and the customer will probably ask you why they're paying you since nothing's changed in the interface."

      Amen to that brother.

      I just had the same experience again the other day. The "CEO" turns to me and says, "So for tha past week you've only worked on the login page?"


      It *is* correct, but it's misleading to tag is "webdev specific" issue. It's same in just about any work that has design and programming phases.

      Dev: "I've been working past 3 months on the script part of our 3rd person shooter game engine"
      Boss: "Can I see how it's shaping up?"
      Dev:"No, it's nothing we can demo yet, just couple of demos where a ball hits a cube and the cubes rotate and such"
      Boss: "You're fired"

      Dev:"I've been working the past 3 months on adding heuristics to our virus scanner"
      Boss: "Can I see it?"
      Dev:"Yea, here it is, enable this checkbox"
      Boss:"3 months for a checkbox? You're fired"

      Basically this is why a project leader has some experience in the technologies involved so you don't lead pointless and potentially catastrophic conversations like these. The team leader's job is to understand his team members needs and the resourse a task really takes, and dumb it down to the management so the management has a realistic idea of the work involved.

      In other words, there are not plenty of highly technical jobs, where you can just walk to your boss and tell him: "I've been porting shit from tables to CSS past month" and expect him to have a clue.

    4. Re:As a Web Developer ... by Osty · · Score: 4, Insightful

      You can layer it out a little (one person in charge of database, one in charge of stylesheets/user-interface, everyone else does everything else).

      I've found that vertical ownership works out much better than horizontal ownership. Rather than having one database guy, one UI guy, and everybody else writing glue in between, everybody is a database guy and a UI guy and an everything-in-between guy. Developers own features from the database all the way to the presentation. You get a better, more well-rounded team that understands more of the entire project that way, and you increase both morale and responsibility by letting developers own specific features (if a feature is great, you know who to praise. If it sucks, there's no passing blame to "the database guy" or "the UI guy").

      You'll still need to have domain experts. Not everybody is going to be a SQL guru or awesome UI designer, so you need team members with those skills who can guide design and implementation, do code reviews, troubleshoot issues, etc. Ideally, these "gurus" are also "regular" team members who own their own feature set. The goal is to spread around the knowledge rather than building little castles around specific areas and throwing around blame. That'll still happen, but it's much harder for Feature A to blame Feature C for Feature A's failure than it is for the database guy to claim his work on Features A and C was perfect and it must be the UI guy who made Feature A suck.

    5. Re:As a Web Developer ... by calbanese · · Score: 2, Interesting

      I just finished a 9 year web development career. Decent pay, crappy sites, crappy companies, crappy hours, crappy offices, crappy management, crappy job security. Did the law school thing. Awesome pay, a good firm, crappy hours, amazing offices, intelligent management, good job security.

      I could not imagine going back to work as a developer. I make twice as much as a first year associate in a major firm than I was as a senior developer working on some major web sites. While I probably work longer hours here (though not much longer, to be honest), I am treated much better, in terms of benefits, perks, respect etc. At least where I am (a top 50 NYC law firm), there are no stupid partners who lucked into their positions. The result is that as long as you are good and can get along with others, you will succeed because it is directly in their interest in having smart people working for them. When dealing with miserable middle managers whose lives suck and who seem to just want to be dicks for the hell of it, it doesn't always work out that way. To top it off, the work I do is far more intersting than the upteenth iteration of some crappy flash interface or search engine.

      My advice to everyone in web development: get out.

    6. Re:As a Web Developer ... by evgenk · · Score: 2, Interesting
      This is funny, yet at the same time it's so true. I've been a web developer for almost 7 years now, and it was fun for a while but now I absolutely hate it for all the reasons you mentioned and some more:
      • I hate constantly educating clients about how things work
      • I hate arguing over comments like "this really should not take this long to do, it's a simple change, all you have to do is move this HTML table". Go and do it yourself then!
      • I hate clients who constantly try to sneak in free changes here and there in their lists of comments.
      • All projects are different, yet they are all composed of same modules. They may look different, and have slightly different features, but in the end it's all same.
      • I hate sales for promising things that cannot be delivered.
      I've been working for the same company for last 6 years, but for last 4 years I've been getting more and more into network/systems administration and I love it. Now I manage a data center of 40 servers and doing this is a lot more fun than coding and dealing with stupid clients.

      I still get suckered into doing coding every once in a while but it's mainly maintenance/changes for projects I worked on over the years, and I am the only one who can do it fast, but that will go away eventually.

      In relation to the original topic:
      It is true that there are a lot of jobs out there for web developers, and since more and more applications are now web-based, I am sure there will be even more work out there. So if you are happy being a web developer, stay in this field.

      just my 2 cents ;-)
    7. Re:As a Web Developer ... by telbij · · Score: 4, Insightful

      I've found that vertical ownership works out much better than horizontal ownership. Rather than having one database guy, one UI guy, and everybody else writing glue in between, everybody is a database guy and a UI guy and an everything-in-between guy.

      The tricky part is building such a team. Everyone wants to hire the people with a perfect skillset, hence the insane job requirements that you sometimes see from corporate recruiters. A good vertical skillset in web development makes not only an extremely attractive candidate, but also someone who can easily freelance or do a web startup.

      However rather than complete verticality, most of the benefit can achieve from proper overlap. IE, the designer needs to understand HTML/CSS pretty well. The markup person needs to understand presentational logic and the basics of the language being used. The programmer needs to know HTML/CSS and have good database fundamentals. The DBA maybe just needs to understand the business processes.

      This allows the team members to work together efficiently. The minute the programmer looks down on the HTML guy for religious reasons, the whole project goes to shit. If everyone is at the top of their game and has some idea of what their team members need to be efficient then a team of 4-5 specialists can achieve great productivity. On the other hand, all it takes is one hack designer using Dreamweaver as a crutch and things can quickly grind to a halt.

    8. Re:As a Web Developer ... by Doctor+Memory · · Score: 2, Informative
      everybody is a database guy and a UI guy and an everything-in-between guy


      As long as you don't have to start the project that way. To really get things moving, have the developers, the designer and the database guy sit down and decide what needs to be done, then have the database guy create the core database, the designer come up with the stylesheet(s) and some mock-up pages, and the developers create (or set up) the framework, then everybody gets together to make everything work together. Once that's done, then the developers get to play with the database, the database guy gets to write some code, and the designer gets to tweak the layout and gather content and fsck up the developers by designing pages that require jumping through hoops of flame to populate and validate.

      At least, that's the way the best projects I've ever worked on went...
      --
      Just junk food for thought...
    9. Re:As a Web Developer ... by Osty · · Score: 4, Insightful

      The tricky part is building such a team. Everyone wants to hire the people with a perfect skillset, hence the insane job requirements that you sometimes see from corporate recruiters. A good vertical skillset in web development makes not only an extremely attractive candidate, but also someone who can easily freelance or do a web startup.

      If you're hiring freelancers or contract workers, it's definitely difficult to build such a team. If you're looking to the future and slowly staffing up in a proper manner, then you should have no trouble getting smart people who maybe don't know everything but have an amazing capacity and willingness to learn. Of course, you need to make sure you do spread out the knowledge at hiring time as well. If you hire all SQL programmers, who is going to be your HTML guru who will train the others?

      I'd also like to point out that this vertical split works well in many other types of development, not just web dev.

      However rather than complete verticality, most of the benefit can achieve from proper overlap. IE, the designer needs to understand HTML/CSS pretty well. The markup person needs to understand presentational logic and the basics of the language being used. The programmer needs to know HTML/CSS and have good database fundamentals. The DBA maybe just needs to understand the business processes.

      Depending on where you make the differentiation between "Developer" and "not Developer", your goal should be to get all of your developers to be proficient at all levels. I mention making a distinction because DBAs are often considered Operations (while they may keep your system running, they're not intimately involved in designing and building new features), or your designer is just a Photoshop monkey with a good sense of design and not someone you'd really want coding. For the rest, you play to their strengths but put them in situations just enough beyond their skillset that they will grow and succeed. The other thing here is that by splitting vertically, everybody must grow together. You SQL guru will have to help your HTML guru with his database design and code, just as your HTML guru will have to help your SQL guru with his presentation work. You're forcing teamwork and communication, while spreading out knowledge so that no single person is too valuable (ideally because you're protecting against bad attrition such as a star developer leaving for a different job, but I guess you could use that as a way to slowly outsource everything as well).

    10. Re:As a Web Developer ... by resin8 · · Score: 2, Informative

      I've been using Dreamstime.com quite a bit lately. Their site is not quite as polished as istocksphoto's, but their prices are lower and you'll see many of the same photos.

  2. Work for a hospital by PIPBoy3000 · · Score: 3, Interesting

    Over ten years ago, I started working for a healthcare organization. Initially the pay was low and the jobs were somewhat stressful. Still, it's now become pretty much the dream job. Since we're non-profit, we can actually do things because it's the good and moral thing to do, rather than lining our pockets with money. Since it's healthcare, there's a fair amount of money to be had, purchasing interesting systems and getting to play with cutting edge technology. The atmosphere is great and I get along well with my coworkers.

    Bottom line, it's a stable, well-paid, and interesting place to work.

    1. Re:Work for a hospital by apt142 · · Score: 2, Interesting

      I'll happily agree with the parent here that non-profits are the way to go to find satisfying work.

      I work at a much less lucrative non-profit than the poster and the worst I can say about my job is that the pay check is not as large as many of my peers. On the other side, the perks are great. My bosses respect me and they look at decisions in terms of effectiveness and not so much in how much of a profit it will turn. (The difference between the two is subtle but important.) I can freely experiment in a lot of the technologies since the cost of entry into many of them is free.

      I get a lot of satisfaction out of my work knowing that any process that I can fascilitate and reduce the time we spend on it helps somebody in the community. And most of the rest of the employees here think I'm a savior for bringing technology into a world that has skimped on it out of a perceived necessity.

      The only legitimate complaint I have is in the area of conpensation and even that isn't terrible.

  3. work for someone by Loconut1389 · · Score: 2, Interesting

    Ever changing end user demands, request for new and/or unproven technology eg "Oh, this thing called Ruby just came out yesterday, I'd like to have a site in that.. Or this new ajax thing"- now these things are old, but when they were just fresh out in the wild, customers wanted it because it was the 'new way'. I hate huge projects where the user changes their mind on something major halfway through and that requires a rewrite of nearly everything you've done, or you find yourself shoehorning things in even when you tried to anticipate features they haven't asked for but will think of or would be nice.. I always found myself giving them way more than they wanted and always ending up with them wanting more. Drives me batty, plus I'm a contractor, so I have to deal with a middle-man who deals with the customer- never play telephone with web-design, it makes it even harder and you get stuck needing input on something and it takes 3 days to get an answer. Ack!

    I don't have a solution for you, I'm now working in an electronic engineering company doing the software side of things and am in way over my head as far as the electronics is concerned, but I'm learning and am paid well- its a great job that's not on contract. Don't do contracts unless you've got lots of customers and other people to help you, otherwise you just get all the headache managing things- there are in fact advantages to working for someone else, as much as I like being on my own.

  4. Heh by aftk2 · · Score: 2, Insightful

    Definitely not stable - I agree with all the other opinions posted. You constantly have to be on your toes, both from a front-end perspective (understanding HTML/XHTML, JavaScript, CSS, etc...) as well as from the programming perspective (different options like ASP.NET w/C# or any other myriad languages, Java/JSP, PHP, Perl, Ruby, etc...) And as if it didn't get worse, the languages themselves seem to change as frequently as the which ones are in vogue (take PHP, for example.) And then, at a higher level than even the web development languages, you have the various frameworks that they utilize (Struts, Ruby on Rails, and others).

    But it can be interesting - if you want interesting more than you want stable, I'd suggest trying to find a startup. Or better yet, work on your own projects in your spare time, and try and spin them off into things that you can do full-time, working for yourself. This is ultimately what I want to do, but it ain't easy. Plus, you need to find an employer who is amenable to this and won't try to claim your off-duty work as their own.

    --
    concrete5: a cms made for marketing, but strong enough for geeks.
    1. Re:Heh by misleb · · Score: 2, Interesting
      Definitely not stable - I agree with all the other opinions posted. You constantly have to be on your toes, both from a front-end perspective (understanding HTML/XHTML, JavaScript, CSS, etc...) as well as from the programming perspective (different options like ASP.NET w/C# or any other myriad languages, Java/JSP, PHP, Perl, Ruby, etc...) And as if it didn't get worse, the languages themselves seem to change as frequently as the which ones are in vogue (take PHP, for example.) And then, at a higher level than even the web development languages, you have the various frameworks that they utilize (Struts, Ruby on Rails, and others).


      I definitly wouldn't recommend that anyone try to be both a frontend and backend expert. I've found tjat good HTML/CSS design and programming are not skill sets with much overlap. Very few people can do both really well. I would suggest that anyone serious about making solid web apps team up with someone (or many people) to complete a well rounded set. You many think "I am a Perl/PHP/Ruby/Java whiz, I can do HTML good enough..." No. You can't. Don't even try. Find a good framework with proper MVC model so you can decouple the front end from the backend and find someone (or a whole team) to complement your skills.

      Although Javascript is a bit of an exception to the front-end/backend separation. As a programmer, you'll probably want to take on a lot of Javascript to help the designer.

      I can't tell you how much my web development job satisfaction improved once I gave up on trying to be an XHTML/CSS expert. Now I can just ask the designer, "Do you have the layout done yet so i can hook it into the backend?"

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  5. Web Developer by Thyamine · · Score: 4, Interesting

    I've been doing web development for a few years now for a consulting company. Initially we just started with our own internal web applications for managing projects, time, expenses, all of that. Eventually we started developing web apps for other clients intranets until it got to the point where I couldn't manage it all myself. We hired two other developers and I took on more of a management role, along with continuing to develop and work on existing applications.

    Not everyone wants to be involved with management, but if you enjoy web app work, perhaps you'd enjoy trying managing others and using your experience to help them.

    --
    I will shred my adversaries. Pull their eyes out just enough to turn them towards their mewing, mutilated faces. Illyria
  6. Business Aanalyst? by plopez · · Score: 2, Insightful

    Since offshoring is becoming all the rage (though there is some backlash) if you are articulate and can write well, use your development experience as leverage to become an analyst. In fact, there are alot of places an analyst could be used. If you need to develop these skills more, take a couple of classes.

    One of the posts mentioned health care as a interesting industry. I will reccomend the energy industry as it is huge, heavily subsidized (the gov't will not allow them to fail), making huge sums of money and some of the problem domains (earth scienes, environmental compliance) are a bit more intersting than your typical ecommerce site.

    Best of luck on the change...

    --
    putting the 'B' in LGBTQ+
  7. Having a bad streak of luck myself right now by Qbertino · · Score: 3, Interesting

    I am a professional freelance webdeveloper at the end of cash resevers with no new deals in sight. It isn't nice, especially with a family and bills to pay. However I know what you're talking of but don't think the technology diversity is a downside. Most people do various technologies for the fun of it. I've done a bazillion different ones in the last 3 years and now I will take the chance and start to focus.

    If you don't like switching the technology every odd month - then don't. It's that simple. There are countless OSS solutions out there, one better than the next. Pick one server side and one client side and stick to that. Zope/XUL, Typo3/Flash Java/Java, OpenLaszlo, Joomla/Ajax, Symfony/XHTML ... whatever you fancy. Stick to it and specialize and do ALL your stuff from here on down with only that technology. See to it that you join the core team of that project and you've no reason to switch solutions ever again.

    I know a webdesigner who does EVERYTHING with ExpressionEngine (a commercial PHP/MySQL Weblog/CMS that's popular amoung designers). It uses some hairbrained Template Level PL for small logic actions. Some more webappy things he does are a total mess and totally destroy the concept of MVC but all the websites he puts out are top notch and easy to operate for his customers. He knows his way around that CMS and customers don't question him.

    After years of exploring all the neat and fun OSS webtechnologies and after 3 years freelancing in the field I'm slowly growing old and will bite the bullet and start to focus. Allready I've done a few jobs with Joomla. Since I'm building a larger PHP webapp just now I'll probably chose a PHP CMS to dive into. And since I'm in germany it probably will be Typo3 - allthough I hate the beast.

    Bottom line: Specialize and focus. That will bring you further than eternally trying to be the jack of all trades.

    --
    We suffer more in our imagination than in reality. - Seneca
  8. Grow with the job a bit by pkesel · · Score: 2

    I've been developing for over a dozen years, from PC database in the Clipper days, to Unix C/C++, now to J2EE and web. Rather than focus on technology I focused on understanding what it takes to be successful in software. The most skilled, sophisticated coder isn't going to be successful if they're solving the wrong problem, or part of hte problem, or someone else's problem. Or if their solution isn't appropriate. The organization isn't going to remain successful after launch if the design or the technology isn't somethign that can be maintained by the staff that's going to follow up the initial development, or if non-functional requirements regarding the need for change are ignored. Focusing on understanding that part of the software problem has me moving into a Director of Technology position at age 35. I went into a firm applying for a project lead position and when I was done with the interview the VP told me to go home and figure out what it would take to be their director. It sure wasn't because I know Struts/Hibernate/Spring/"buzzword of the day". The industry as a whole needs more people who can think above the keyboard and know how their organization works and what it needs to survive. If you were on a failing software project recently, was it because you and the end-developers couldn't write code? If you're in a mess of a software house, is it because the team couldn't make Spring or Hibernate or Struts or whatever work? Not very likely. If you want a long term career, solve the real problems of IT and the business that relies on IT.

    --
    - Sig this!
  9. Back in the day... by penguinstorm · · Score: 3, Insightful

    Back in the day when I had an employer who respected what I did, came into the web world with an open mind and interested in success, and didn't second guess everything I did it was great.

    There are two phrases any client should never use:
    1) "Make it look exactly like this."
    2) "My friend has an 8 year old kid he says built him a web site."

    A bad client can be a real problem. It takes a lot of work to find a good one.

    --
    Skot Nelson music is my saviour / i was maimed by rock and roll
    1. Re:Back in the day... by protohiro1 · · Score: 2, Insightful

      Man, screw those people. That is our new policy at our company. If someone tells us we cost to much and someone else can do it better, cheaper we let them go. I don't need people that are going to nickle and dime. If they really think that web dev is easy and shouldn't cost money they can do it on their own.

      --
      Sig removed because it was obnoxious
  10. Frank, there's something wrong. by Anthony+Boyd · · Score: 4, Insightful
    I have been a web developer for seven years now. I have had some moments of success, but mostly down moments with low pay, less than stable work, and unemployment.

    Does that sound odd to anyone else, or am I just disconnected from some greater reality?

    Frank, I've been doing Web stuff since 1994. I started with very little know-how -- I went to college to study English, not programming. Over the years I spent time as an artistic Web Designer & Photoshop monkey, then usability expert, then a JavaScript & Perl CGI developer, then PHP, MySQL, and eventually I just decided to say yes to everything. I'll try anything. And what is important to note is that my salary has steadily gone upward -- huge leaps upward during the boom, and then it was flat for a while, and then I started working for myself, and gave myself a pay raise. ;)

    I have more work than I can accept. In fact, I've probably disappointed a few business people lately because not only was I too overloaded to take their work, but my subcontractor was too. How does this sync up with "low pay and unemployment" problems?

    I have to wonder. What is your skill set? In seven years, you could and should have learned quite a lot. You should be much more competent, and thus much more in demand, than any young bloods coming onto the scene. Your skills should be apparent to those working with you -- "oh, he's the guy who does _____." For me, it's "he's the guy who fixes the Web site when our employees break it." There should be certain things you have zero doubts about as far as your skills are concerned. For me, it's PHP and MySQL, with all the ancillary buzzwords as a given (XHTML, CSS, Ajax). Can you easily and readily point to your strengths, and can your peers?

    Lastly, what are you doing to market yourself? You don't provide links to your sites or portfolio in your story submission. With your mention of low pay & unemployment, I wonder about your networking too. Have you mass-mailed every friend & relative in your address book, asking for work? Have you kept relationships with the people who have hired you in the past?

    I ask because it seems odd that after 7 years, this is the story you have to tell. And that makes me worry about the next thing you jump into. How many of the issues you have right now are due to the job itself, and how many are due to your own networking/skillset/learning/marketing deficiencies? If you find that a lot of it is of your own making, then changing jobs is NOT going to help. It will just be a year of euphoria followed by several more years of being brought back down to harsh reality. Think hard before you jump to the next thing. I'm worried it may be more of the same, unless you do some hard self-analysis first.

    1. Re:Frank, there's something wrong. by mdavids · · Score: 2, Insightful

      It depends greatly on where you live, and who your customers are. I've been a web developer for about two years (had done a lot of it in the past, though), since moving to a large town/small city. We came here with a long list of things we could do, and quickly settled on web development because every organisation here that had a web site had a dreadful website. You know the drill: something knocked together by some guy who'd just done a course in Dreamweaver and Photoshop, 90% of the text is an image, every link is a JavaScript onClick() event (why?!?), no page is without some form of god-awful cheezy animation, including the "click here to enter" splash screen which not only gets in your way at the first page, but at every subsection of the site's navigational heirarchy. Of course all these sites are three years out of date, because they just haven't had the cash to hand to pay the original developer to update it for them, and when they do, they find he's moved into another career (presumably following another 8 week course), and has no time for them.

      The problem is that this arrangement is perfectly within their comfort zone. If you tell most small businesspeople that they can have a simple website for hundreds, rather than thousands of dollars, that they can easily update it themseves for free, and that every time they prepare a press release or similar promotional info for the local press, they can copy and paste in into their CMS in seconds and have an up-to-date and informative website rather than an outdated online sales brochure, they will look scared. And they are not hearing this from a dishevelled and manic nerd, but from an attractive and professionally presented young lady (my wife, a relatively normal person who is the public face of our business).

      Every sale we make is a result of a lot of marketing ground work, because what we are selling is, while although undeniably superior to what the competition provides (at half the cost), totally foreign to our potential clients. So we end up with periods of frantic activity interspersed with periods of zero income. We've had some successes with some very satisfied customers, and some very frustrating experiences of the kind described above with some people who think that being a dumb obnoxious bully and being a shrewd businessperson is the same thing. After a very tough couple of years, we are finally keeping our heads above water, but I'm getting very sick of instant noodles and would like to be able to afford a night out at the local pub once in a while.

      The answer seems to be not to move into a totally different line of work (the positions vacant section of our local paper is not sufficient to cover the floor of an average-sized bird cage), but to find complementary work to smooth out the income troughs. In fact my wife, in addition to doing all the administrative and organisational work for us, is now spending a day or two a week doing the same for other businesses around town.

      So the question becomes, what kind of work can be a reliable supplementary source of income for a nearly-but-not-quite full-time web developer?

    2. Re:Frank, there's something wrong. by Anthony+Boyd · · Score: 2, Insightful

      Music? Well, you're a prime candidate for programming. Music & math go hand in hand. So you already have a good start.

      For me it was fairly natural. The Web had just started. I was one of the much lamented AOL crowd that came online when AOL brought in Usenet news feeds. I was publishing a small press journal, and I wanted more exposure. I learned about the Web, and found I could understand HTML enough to create something similar to my journal, online. So I put out a few issues.

      I think in February/March/April/May 1995, I got featured in a few magazines, and was AOL's "site of the day." I had started putting up tutorials for all the things I was learning. I heard that Borland (close to where I was living) was looking for Webmasters. I sent them my URL, along with press clippings. They called, I was hired, and then I parlayed that into more & more.

      If I could give a person any single bit of advice, it would be to be curious. Not black-hat curious. But "hey, interesting technology, wonder if I can pick it up" curious. I hired a guy a while back, Jeremy Meigs, and he was REALLY green. But the thing was, he stayed late learning, he read books, if he didn't know how to do something he figured it out -- even if it meant a little extra effort on his part. He didn't farm the hard stuff out to others. He didn't beg for favors. He didn't say things couldn't be done. Sometimes he would ask me for some pseudocode or something to get him started. Sometimes I'd see him searching Google really hard, looking for a long time for tutorials or discussion forums or any helpful data he could find. But in the end, he'd have a finished project, and he'd be able to speak eloquently on why he built it the way he did. He took the time to really absorb stuff, he drank up knowledge like a sponge.

      Because of that, the fact that he had zero background in programming mattered little to me. To go back to what I said in my original post, I know his skillset. "He's the guy who is good at learning anything technical." So if I ever need someone to pick up a new technology, he's the guy I'd contact.

      So that's my help for you, for what it's worth. Be interested in learning. Be willing to accumulate a body of knowledge, so that after a time, you have a great foundation. Don't rely on consultants, procedures, diagrams, and other meta-chatter. Get into the actual creation of something. Become great at Photoshop, or become great at PHP. Whatever you pick, understand it deeply, and then branch out and apply that deep understanding to new skills. If you do, people will see that, and they will find you valuable.

      -Tony

  11. Glad to be out by liliafan · · Score: 2, Interesting

    I did web development for many years, I tried to get out but you end up doing different jobs if they get the slightest clue that you have experience doing web development they start to pull you back into that.

    For example, I took a job as a system administrator for a large ecommerce company, they had an emergency one day where some perl cgi scripts broke, the developers were flapping around trying to figure it out, I suggested a solution that worked, from that day one I also had web development tasks, when I finished that job my offical title was: IT Manager/Network Manager/Website Manager.

    Second time this happen, unix sys admin for DoD couldn't be further from web development right? Wrong, since being in this job I would estimate about 60% of my time is spent doing tasks related to web development, (I don't mind so much here since the development is very much backend stuff for internal application so less pressure), but it all started because a midlevel manager noticed on my resume when doing some reviews that I had experience in that field.

    I swear next job I am omiting all references to web development from my resume.

    --
    GeekServ Unix Consulting Services (http://www.geekserv.com)
  12. I concur by madaxe42 · · Score: 2, Insightful

    I agree totally - my partner and I work together developing high end eCommerce solutions - we've written a bespoke system, and we pull in high six figures (in pounds stirling) between the two of us month after month - web (particularly eCommerce) development is booming.
     
    Yes, it's a tough job - you have to be prepared to work seven days a week, be on call at 4am, and work 18 hour days (minimum), and put up with shit from clients who don't have a clue. We have a good team insofar as he is a photoshop and design genius, and has a decent working knowledge of PHP/MySQL, and I do all the guts - the javascript, the AJAX, the PHP, the SQL, the server setup, the scalability...
     
    In all - Web development is a tough job to have, but not for the reasons you give... If the work is short, it might be (Sorry about this) because you're not very good.
     
    One piece of advice - find a focus, and stick to it - there's no point in being the jack of all trades and master of none - by this I don't mean a technological focus - I mean a business focus.

  13. Same boat but I evolved by Foofoobar · · Score: 2, Informative

    I was in this boat a few years ago and saw where the industry was going and prepped myself for the changes.

    I specialized in LAMP (Linux, Apache, MySQL and PHP). This skillset will cover the vast majority of jobs on the market. Knowing Photoshop and Flash helps but isn't necessary. You should have OOP running through your veins and understand what MVC is and use it daily. As a web dev, you are also expected to be a sys admin to a certain extent setting up cron jobs, checking security, etc. Also, knowing how to build an e-commerce site, build your own SSH certs and manage public and private keys helps as well.

    Basically, you are a sys admin with a specialization in the web.

    Focus on this kind of skillset and you will be set.

    Also, don't take any job that requires you to know Photoshop, Illustrator, Flash and Visual Basic; these are red flags that tell me the job won't last a month and that the employer doesn't really want a web dev and isn't sure what they are looking for.

    Which brings me to another good point. People who ask you to know IIS, Apache, Windows, Linux, Visual Basic, PHP, .NET and Java haven't got a clue as to what they want. Don't bother with these guys (unless they happen to be a hosting company and you do happen to be multilingual).

    --
    This is my sig. There are many like it but this one is mine.
  14. Obligatory by WedgeTalon · · Score: 2, Funny

    Rob say Code Monkey very diligent
    but his output stink
    his code not functional or elegant
    what do Code Monkey think
    Code Monkey think maybe manager oughta write goddamn login page himself
    Code Monkey not say it out loud
    Code Monkey not crazy just proud

    http://www.jonathancoulton.com/2006/04/14/thing-a- week-29-code-monkey/

  15. Enjoy Your Work! by mongus · · Score: 2, Insightful

    I'm of the opinion that if you don't enjoy your work you should find something else to do. Life's too short to stay in a job you hate. Maybe web development isn't for you. Find something you like to do and head in that direction.

    My average job length is about a year because I get bored quickly. For developers changing jobs is often the easiest way to get a pay raise.

    If you do enjoy web development there are plenty of good jobs out there. Be picky! Find one that you will enjoy doing for a while. The environment makes all the difference. Meet the people you'll be working with. If you don't get along with them you're all better off if you find something else. You may have to find temporary work while you're looking for a good job but in the end you'll be much happier if you take the time.

    My current employer found me on Dice.com. After posting my resume I was getting several calls a day. Many of the calls were only good for laughs but at least they gave me options.