this post was submitted on 09 Nov 2023
1 points (100.0% liked)
Entrepreneur
0 readers
1 users here now
Rules
- No Personal Attacks - criticism of ideas is allowed, attacking people is not.
- Self Posts Only - links can only provide supplementary material. Your post must contain enough content to have a discussion.
- No “How To Get Rich Quick” posts - This community is not about making a quick buck. Posts asking the community how to make $X, without making specific reference to a reasonable idea, are not tolerated.
- Avoid unprofessional communication - Please treat fellow entrepreneurs like respected coworkers, label conversations if NSFW and avoid deliberate provocations.
Please feel free to provide evidence-based best practices, share a micro-victory, discuss strategy and concepts with a frame work, ask for feedback, and create professional conversation. Treat every post as if you're at work and representing the best version of yourself.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You absolutely shouldn't have to brainstorm how to fix your programmer's bugs.
It sounds like you two weren't a good fit. Maybe he was unethical, or maybe there were other issues. You wrote that you were eventually telling him "how" to do things; that's not a level of interaction you should have to take or that most programmers I know would be comfortable with. A non-technical boss should just be telling developers the requirements and ideally the "why", not the "how".
You might want a technical cofounder, or an engineer who'd be willing to walk you through best practices in working with them. This will help you learn and set expectations for leading programming teams in the future.