4 ms·

I've worked for many startups. 1) I wrote redundant code for displaying the same information in a ASP master page project. Literally copying and pasting, made i

I've worked for many startups. 1) I wrote redundant code for displaying the same information in a ASP master page project. Literally copying and pasting, made it very hard to organize. 2) I didn't take any interest in the full stack when the company needed a full stack developer. I only focused on front end when the back end needed help. 3) I broke the key off inside a rackmount server case accidentally and didn't tell anyone. 4) I built a rigid framework on top of Symphony, a polymorphic ORM and a slow lazy loading system that is hard to write code for and make updates to. I think this is why the company didn't sell. 5-10) I didn't finish the product for the startup and it sputtered.

jpm_sd 8y ago
Haha, this is reminiscent of Chunk's confession in The Goonies: https://www.youtube.com/watch?v=Q5UG7ISJfP0 https://www.youtube.com/watch?v=Q5UG7ISJfP0
mlthoughts2018 8y ago
> "2) I didn't take any interest in the full stack when the company needed a full stack developer." I would consider this a good, ethical thing to do, and not at all unethical. The company's needs don't always come before your needs to protect your specialization and your work experience, not even in early-stage start-ups. It's on the management to get the right people, not to trumpet around some disingenuous "everyone wears many hats" philosophy to squeeze inappropriate work out of you. It can really be damaging to your career if you get hired into a start-up to do X, but then because "wear many hats" or "we're a lean shop" or whatever nonsense, you only spend your time doing Y. After that, if your real passion was to work on X, it can be really hard to get employers to look at you seriously for hiring for X. You'll be pigeonholed into Y. Since employers ought to care about career goals and growth of their staff, it definitely makes this sort of thing more the employer's fault than the employee's. So, I would say item 2) is not unethical at all -- and in fact it's deeply important for people around the industry to take a hard line with this sort of thing when they need to protect a career-goal specialty.
- megamindbrian2 8y ago
  Thank you.
overcast 8y ago
You broke a key?! How scandalous!
- cimmanom 8y ago
  It's not the breaking that's unethical. It's the not telling anyone.
  - megamindbrian2 8y ago
    Yup. I still think about turning the case on its side to look for wall attachment brackets and the key snapping off. I could have easily bought a replacement lock and screwed it in without anyone noticing.
NullPrefix 8y ago
>3) I broke the key off inside a rackmount server case accidentally and didn't tell anyone. You monster!
oakwhiz 8y ago
In my experience, those keys are usually made of incredibly cheap metal.

jpm_sd 8y ago

Haha, this is reminiscent of Chunk's confession in The Goonies: https://www.youtube.com/watch?v=Q5UG7ISJfP0 https://www.youtube.com/watch?v=Q5UG7ISJfP0

mlthoughts2018 8y ago

> "2) I didn't take any interest in the full stack when the company needed a full stack developer." I would consider this a good, ethical thing to do, and not at all unethical. The company's needs don't always come before your needs to protect your specialization and your work experience, not even in early-stage start-ups. It's on the management to get the right people, not to trumpet around some disingenuous "everyone wears many hats" philosophy to squeeze inappropriate work out of you. It can really be damaging to your career if you get hired into a start-up to do X, but then because "wear many hats" or "we're a lean shop" or whatever nonsense, you only spend your time doing Y. After that, if your real passion was to work on X, it can be really hard to get employers to look at you seriously for hiring for X. You'll be pigeonholed into Y. Since employers ought to care about career goals and growth of their staff, it definitely makes this sort of thing more the employer's fault than the employee's. So, I would say item 2) is not unethical at all -- and in fact it's deeply important for people around the industry to take a hard line with this sort of thing when they need to protect a career-goal specialty.

megamindbrian2 8y ago
Thank you.

overcast 8y ago

You broke a key?! How scandalous!

cimmanom 8y ago
It's not the breaking that's unethical. It's the not telling anyone.
- megamindbrian2 8y ago
  Yup. I still think about turning the case on its side to look for wall attachment brackets and the key snapping off. I could have easily bought a replacement lock and screwed it in without anyone noticing.

NullPrefix 8y ago

>3) I broke the key off inside a rackmount server case accidentally and didn't tell anyone. You monster!

oakwhiz 8y ago

In my experience, those keys are usually made of incredibly cheap metal.