5 ms·
>It is someone else's business, and I am there to do what they ask me. Which may or may not match to what they need, but that's not for me to decide. I know th
by dominotw 9y ago
>It is someone else's business, and I am there to do what they ask me. Which may or may not match to what they need, but that's not for me to decide.
I know that this is the right idea, but it is so painful to build something you know is stupid and waste of time. Its impposible to go home happy knowing what you are building is crap.
- iamacynic 9y agochoose better people to work for. you are not a helpless victim.
- thesagan 9y agoNot a helpful comment. Some people have more leverage than others.
- quantumhobbit 9y agoIt is also really hard to tell before hand. Companies change over time and can be very good at hiding their red flags.
- theparanoid 9y agoIt's easy to ignore red flags. We're rationalization engines.
- ThomaszKrueger 9y agoI look it this way: if I were good/smart/eager enough to decide if something is stupid or a waste of time, I may think about becoming the entrepreneur myself. I am not that person. I am a tool. Someone is paying me to develop something that it is important at least to them. I am a professional, I get things done for other people.
- mgkimsal 9y ago"I am a professional, I get things done for other people." I agree, but only if people want to pay "professionally" for it. Additionally, there can be problems with this if you're working someplace where your job is potentially at risk if the project fails. It's very hard to take strategic direction from folks who have golden parachutes in their contracts. Succeed or fail, they'll be OK, but when you can see the project is DOA, you now have to spend some time preparing to look for the next job/engagement/etc. I realize not all situations are like this, but have seen enough to understand it happens. You can be professional, but also have to understand that sometimes your best interests and the project's best interests may not line up, and plan accordingly.
- ThomaszKrueger 9y agoI learned the hard way to always be prepared to move on. I keep myself current. I actually assume the project will fail and prepare for it. If it succeed that's great news. I never had and probably never will have golden parachutes. My insurance is what I know and why I do. It must be valuable for the marketplace, not just for the company I am currently working for. That is my duty.
- mgkimsal 9y ago> I actually assume the project will fail and prepare for it I do as well, but it is always a bit of a conflict in the back of my mind wrt feeling 100% dedicated to someone else's project. I want to feel that I'm committed 100%, but always have to be preparing for "this will not work out, what is plan B?".
- ido 9y agoAt some point regardless of feelings you just shouldn't be 100% committed to some else's project, of which you have very limited control (if at all). You can be 90% committed and a professional and still get a lot done and do great work.
- ThomaszKrueger 9y ago
- virmundi 9y agoI've had a lot of existential issues with this. What makes me feel better is that the system in the moment is what matters. Everything gets destroyed in the end as per every world view (goes to a heat death, gets destroyed by Yahweh and a new Earth comes about, wolf eats everything). Nothing you build will last more than one or two generations, statistically. Just enjoy making the thing and the process of trying to solve a problem. Maybe pick which problems you work on.
- ryandrake 9y agoI've spent plenty of time in my career building stupid things. While I'd prefer to build non-stupid things, as long as I'm getting paid well for it, I will happily build your stupid thing. If you get hung up on needing more control over what you're building, you actually have a few other options: 1. Take on a hobby in your free time. 2. Work for a different company, where developers have more of a stake and help define the product (there are few but they exist). 3. Moving into a "product management" role where you're defining features and requirements, etc. 4. Put your ass on the line and gamble on starting your own company.