> In 1995 I quit my regular job as senior web engineer You had the job title "senior web engineer" when the web was 4 years old. That's pretty cool.
The shittiest project I ever worked on
31–40 of 187 posts
Re: The shittiest project I ever worked on
#32Re: The shittiest project I ever worked on
#33The reason the fee was there was to pay for the 0800 thing. Some executive rightly saw that paying you to render that useless would free them of that service and the need for the fee (which i bet was not turning a profit) But, since big companies run on cargo cult... that happened.
Re: The shittiest project I ever worked on
#34Although it's a fun read, it's a classic example of diving into coding without giving a project it's due diligence. There's nothing that's derailed my projects more consistently when I started out as not understanding the user's needs. They'll never tell you what they want, only what they don't want after you deliver something. I think that's the key difference to an experienced dev/BA. One who can actually sit with…
Reminds me of an old saying: "If you don't know how to do it, you don't know how to do it on a computer."
Re: The shittiest project I ever worked on
#35Earlier quoted context omitted.
If a static page is the right answer, why would you not say so? Scales effortlessly for one thing.
I think it was a joke.
I remember finally turning down one project after failing to convince the small businessman that his site didn't need an unskippable flash intro with techno music.
Edit: I think that nowadays web 2.0 needs have been replaced with 'BIG Data'. I have a current client whose data set is less than 30 MB, but he insists that it is not just big data, but HUGE data! Which is a shame, As it is an interesting problem he has, but I will probably turn it down too.
Re: The shittiest project I ever worked on
#36> In 1995 I quit my regular job as senior web engineer You had the job title "senior web engineer" when the web was 4 years old. That's pretty cool.
Re: The shittiest project I ever worked on
#37> In 1995 I quit my regular job as senior web engineer You had the job title "senior web engineer" when the web was 4 years old. That's pretty cool.
I had a "Senior Software Engineer" title after only about 2-3 years of real-world programming experience, at age 23 or so. I had shipped a couple games as lead by then, so it wasn't entirely unearned.
Re: The shittiest project I ever worked on
#38Re: The shittiest project I ever worked on
#39> In 1995 I quit my regular job as senior web engineer You had the job title "senior web engineer" when the web was 4 years old. That's pretty cool.
US corporations tend to do that. Instead of a big raise, small raise and "senior". That can even be negotiated in hiring, so you may join as senior for a position just created in the market.
Re: The shittiest project I ever worked on
#40I worked there for about a week before I quit in frustration.