4 ms·

1. Don't quit immediately if you have choice, I will probably disagree with this. 2 and 3 is almost similar. Lots of us here try to build something cool, if yo

1. Don't quit immediately if you have choice, I will probably disagree with this. 2 and 3 is almost similar. Lots of us here try to build something cool, if you think your product will be loved by others stay there and just finish product, do not think about code, hardware spec and anything other than product, just build that product, make it work. Clients will not look at your code or how you designed your system, they will look for result, it works or not. Just make it work and when others (especially management) are happy, tell them, hey guys because we had deadlines and other shit, we built product with shit design, let us work on it and fix it, otherwise when clients ask for improvement we will fail. when management is happy they will give you a time to fix shit. I guess in every product there are lots of bugs and shit stuff inside, but they are selling and improving, as Donald Knuth said "Premature optimization is the root of all evil". If it doesn't work than you can leave, just don't forget when deadlines are coming every "cool" startup, every "cool" hardware creates monkey patch, just to make it work and sell well.

antocv 12y ago
No offense but you are expressing is what I hate the most - "just get it done", "just make it work", cut corners, allow shit design Its not going to lead to any product at all, its not bad low quality product, its shit noone would ever want to touch with a pole, hardly to pay for. Thats the state of the product. In fact, what these managers and some developers do is generate more shit by taking more time, more unnecessary code and tools, and more resources involved, I think they hired this many people totally unnecessarily, like more than half could be fired and noone would notice.
- tuyguntn 12y ago
  "its not bad low quality product, its shit noone would ever want to touch with a pole, HARDLY TO PAY FOR" - then you got your answer, if you are doing thing which nobody needs or no one wants to pay for it, just leave. But consider the fact, you are tech-guy, for many tech-guys some products may seem useless, but there are lots of people who may pay for it and use it everyday. Saying "leave your job" is very easy, because as OP I am not leaving my job, you are going to leave. think about cases, eliminate best cases if they are unrealistic. - best case: top management says: ok, seems you got it right, lets make product as this guy said. - worst case: you leave your job - something in the middle(1): you will make that shit happen, you get salary for it, if product fails you leave - something in the middle(2): same with above, but you don't leave, you try to make product better - something in the middle(3): you fight for better design, better product, present your arguments, show people that you know more about product, about market than any other managers, so they may consider your facts
mak4athp 12y ago
Technical debt is difficult to measure, but this is a great way to accumulate a tremendous amount of it. Engineering managers and product designers have nightmares about people who work this way.
- tuyguntn 12y ago
  "Engineering managers and product designers have nightmares about people who work this way." - exactly. but OP described his managers as opposite, either OP is not so smart and couldnt understand what and how they are building product or his engineering managers are not smart. In case of dummy managers, they have 2 options: (1)either they listen their engineers and talk with higher management about product and make it better (not the case with OP) or (2) their engineers create shit and fail product, then engineering managers will pay for it with their career. radical way, but someone should be blamed.

antocv 12y ago

No offense but you are expressing is what I hate the most - "just get it done", "just make it work", cut corners, allow shit design Its not going to lead to any product at all, its not bad low quality product, its shit noone would ever want to touch with a pole, hardly to pay for. Thats the state of the product. In fact, what these managers and some developers do is generate more shit by taking more time, more unnecessary code and tools, and more resources involved, I think they hired this many people totally unnecessarily, like more than half could be fired and noone would notice.

tuyguntn 12y ago
"its not bad low quality product, its shit noone would ever want to touch with a pole, HARDLY TO PAY FOR" - then you got your answer, if you are doing thing which nobody needs or no one wants to pay for it, just leave. But consider the fact, you are tech-guy, for many tech-guys some products may seem useless, but there are lots of people who may pay for it and use it everyday. Saying "leave your job" is very easy, because as OP I am not leaving my job, you are going to leave. think about cases, eliminate best cases if they are unrealistic. - best case: top management says: ok, seems you got it right, lets make product as this guy said. - worst case: you leave your job - something in the middle(1): you will make that shit happen, you get salary for it, if product fails you leave - something in the middle(2): same with above, but you don't leave, you try to make product better - something in the middle(3): you fight for better design, better product, present your arguments, show people that you know more about product, about market than any other managers, so they may consider your facts

mak4athp 12y ago

Technical debt is difficult to measure, but this is a great way to accumulate a tremendous amount of it. Engineering managers and product designers have nightmares about people who work this way.

tuyguntn 12y ago
"Engineering managers and product designers have nightmares about people who work this way." - exactly. but OP described his managers as opposite, either OP is not so smart and couldnt understand what and how they are building product or his engineering managers are not smart. In case of dummy managers, they have 2 options: (1)either they listen their engineers and talk with higher management about product and make it better (not the case with OP) or (2) their engineers create shit and fail product, then engineering managers will pay for it with their career. radical way, but someone should be blamed.