6,107 karma · joined February 3, 2016
> When you're used to the kind of income that software can generate farming anything seems like very hard work, even when it works well.
Even if that’s true, so what? They didn’t ask, is this a better path to getting rich than working at a FAANG. They asked if anyone knew how to do it. The only correct answer for the people in this thread would be “nope, no idea”. Thus my point that they’re not being “realistic”, they’re just well-actuallying someone without having any relevant knowledge.
Seek to understand, don’t just be a wet-blanket.
Edit: see also the top-level comment from the former actual coffee farmer who said that there’s not that much to do outside the harvesting season. This goes to my actual point, which is that your experience in a totally different field doesn’t translate. Now that’s hilarious.
Meta-advice, find people who actually understand the business and get their opinions. This forum is great for CS startups, but it’s full of people who think their success in one field means they are experts in everything they’ve read an article about. Be skeptical.
Hardly, you don’t know anything about how difficult it is to do what they’re trying to do. For all you know it’s a crop that essentially grows itself and has a huge market demand so selling is easy. Your experience in unrelated small businesses in another country has very little bearing.
Is that actually true? I’m very curious if there’s any theoretical evidence that a society where everyone is at minimum “middle class” can exist.
Extraordinary claims require extraordinary evidence.
Are there people who this is out of reach of? Yes. Would it be cool if it were free? Of course. Is it crippling debt that makes a comfortable life impossible? Don’t be absurd.
https://www.atlanticbay.com/knowledge-center/history-of-mort....
You should be aware that this thing where you pretend to be confused because you don’t like the answer is a pretty weak defense. You might be impressed with your mental gymnastics, but I assure you that the court will not be.
We have the abstraction of job titles or categories to help us reason about what a job is. We do this for a variety of reasons, but in this case the reason to do it is to help people understand whether this advice might apply to them. Ultimately, a job is whatever it’s primary goal is, and you said yours is to empower junior staff who report to you. That makes you very different from many (most?) senior/staff engineers I have met, who are primarily metric’d on their engineering work. Since your primary job is a management function and you write a lot of code, that makes you a manager with some (or many, pick whatever modifier seems appropriate to you) engineering responsibilities.
Bringing it home, if a reader is an engineer (or IC if you prefer to avoid the fraught term) and not a manager, this advice doesn’t apply to them very strongly. Yes they should care about junior colleagues, and they should absolutely make time for deliberate peering and mentoring, but they should focus on doing engineering (which can include docs writing etc) primarily.
What does that mean?