2 ms·
If you worked for a small company (let's say < 100 people) it's not a good idea, as you will actively focus all your energy destroying the jobs of your former c
by rvnx 2y ago
If you worked for a small company (let's say < 100 people) it's not a good idea, as you will actively focus all your energy destroying the jobs of your former colleagues and take their marketshare (in some way, even indirectly), and these ideas with small teams usually require deep secret knowledge.
If it's a huge company (e.g. you work for a large telecom company and launch a new telecom company), then it's fine because you started only from one brick, and had to figure out most of the pieces by yourself.
- ArdentAardvark 2y agoThis is ridiculous. There are no rules, not even ethical ones, preventing you from starting a competing company. Especially since generally we don't start companies "putting our effort into destroying the jobs of our former co-workers". That's an absurd take.
- rvnx 2y agoIt's like if you work in private army A and go to create private army B to fight against army A on the same territories. No reasons to be surprised if private army A colleagues don't like your move.
- mtndew4brkfst 2y agoWhy should anyone care about the emotional state of members of a "private army"? Why would this be one of your analogies in the first place?
- immibis 2y agoI prefer "treat others as they would treat you" as a moral principle - or slightly better than they would treat you. How do you think your company would treat you, if they found a developer that did a better version of whatever you're doing? If you found a better way to do whatever your company is doing, the answer should be the same.