Live data from Hacker News

The shittiest project I ever worked on

blog.plover.com

31–40 of 187 posts

Re: The shittiest project I ever worked on

#31

> 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

#33
post #30

The 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.

Wrong.

Re: The shittiest project I ever worked on

#34

Although 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…

"One who can actually sit with the stakeholders and build the system on paper and go through each of the problems as the diagrams connect."

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

#35
post #13

Earlier 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.

Bingo. A surprising number of modern web problems can be solved via static pages - speed, usability, scalability etc.

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.

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

#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.

But I'm sure software had existed a long time before you started. The GP's point was that being a "Senior web engineer," when the web itself has only been around a few years is impressive.

Re: The shittiest project I ever worked on

#38
Sounds like poor contract negotiation more than anything. Fixed quotes are very tricky things to navigate. I simply don't go there. If the client insists then I try to negotiate a fixed budget, then when the budget us running dry they can extend the budget or reduce scope. If they don't agree to that I walk.

Re: The shittiest project I ever worked on

#39
post #31

> 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.

Not only in the US, unfortunately. I've even seen company creating other kind of superlative, when lead, senior, manager or director was taken. What about "International Senior Art Director" (even if your job is basic graphic designer in a 25 persons company) ?

Re: The shittiest project I ever worked on

#40
The shittiest project I ever worked on was a php project that was converted from another language (I don't remember which one). This doesn't sound bad, except they used software to automatically convert it. The PHP code had no comments, minimal white space, and the variables were all hex. My job was to fix bugs.

I worked there for about a week before I quit in frustration.

Post reply on HN