I’m a 25-year-old guy who loves coding but struggles with job hunting due to Asperger’s and depression. My uncle, who’s 51 and not a coder, recently got into a startup and asked me to create a frontend for their app.
At first, I agreed to help, but now I’m having second thoughts. The ‘design’ they gave me is just some PowerPoint slides with website screenshots. The backend data is a mess too – it’s JSON but doesn’t have enough info for the frontend. Instead, they want me to render HTML strings and run JavaScript code sent from the backend. What a headache!
I told my uncle I can’t do it. Now my parents are upset with me. Dad says I should just follow the design as best I can, and Mom thinks I’m being lazy.
I feel bad, but I don’t want to make something that’s intentionally broken. My family thinks I’m being difficult, but I’m worried about messing up their project. Am I in the wrong here?
Edit: Thanks for the feedback. I know I’m lucky to have a supportive family while job hunting. I’m working on being less ‘exhausting’ to deal with. And no, I don’t expect payment for this – it was supposed to be a favor. I just can’t make something good with the current design and API setup.
hmm, sounds like a tricky situation! have u tried explaining to ur uncle why the current setup might not work well? maybe u could suggest some simpler alternatives that’d be easier to implement? it’d be cool to hear more about what kind of app they’re building - maybe there’s a creative solution that could work for everyone?
nah, ur not wrong. sounds like a messy project tbh. family stuff can get complicated, but don’t let em pressure u into a bad situation. maybe offer to help find a pro developer instead? that way u stay supportive without getting stuck in somethin u can’t handle. just my 2 cents
As a professional developer, I can attest that your concerns are valid. The project’s current setup raises serious red flags. Rendering HTML strings and executing JavaScript from the backend is a security nightmare and goes against best practices. It’s not just about following a design; it’s about building a secure, maintainable application.
Your reluctance isn’t laziness; it’s a sign of expertise. Perhaps you could offer to consult on the project instead, helping them understand why their current approach is problematic and suggesting more robust alternatives. This way, you’re still contributing without compromising your professional standards or potentially damaging their startup’s future.
Remember, sometimes saying no is the most helpful thing you can do, especially when it comes to technical decisions that could have long-term consequences.