Highly recommend this book on the topic: http://momtestbook.com/
3,044 karma · joined March 14, 2013
Highly recommend this book on the topic: http://momtestbook.com/
I think this part shows that whether it's easier to make more as an employee or self-employed is highly regional. In large, competitive tech centers, where FAANG companies are, the demand and competition for talent is high and fierce, driving salaries significantly higher than what you might normally expect. The cost of living in such places also tends to be astronomical.
In other places, say medium-sized cities that are not known as tech centers, that dynamic doesn't exist. In my experience, this means that the income you can achieve as a self-employed (and often remote) software engineer far exceeds the general salary "ceiling" of that local region (and I'm talking about North America here, not far-off places). So you may not quite achieve FAANG level compensation (although I'm sure some do), but relative to the cost-of-living you're doing quite well if not better.
https://impossiblesoftware.com/
https://developers.magisto.com/ (not exactly what you're looking for, and very expensive, when I inquired)
Anyway, I ended up rolling my own solution (not an API, but for internal use only).
So this was my point in bringing it up: "We're faster than the other APIs out there" is a much more direct benefit to communicate to me as an API user than "We use GPUs, which makes us fast, faster than the competition, who don't use GPUs". The latter version has me making assumptions and eventually getting to a conclusion that matters to me; why not take me there immediately?
The thing is, as a non-expert in this area, I don't even fully understand whether the real performance bottleneck in such an API is the latency of uploading the image and downloading the result, or the computational processing of the image. So if using GPUs cuts the overall request time by 70%, that's great! If it only affects the round-trip time by 5%, then it's not a huge deal to me. As the domain expert, I'm relying on Pixaven's marketing to educate me on this.
Here's what I don't quite get: why does the GPU differentiation matter to me as a user of your API? I get that you're faster than doing it myself using something like ImageMagick, but are you faster than the other image processing APIs out there because of this? If so, that's what I think you should be touting. If not, whether the images are being processed by GPUs or trained giraffes is not that important to me as a consumer of the API, but I could be way off-base.
That said, your experience provides an important data point too. I would be curious to know whether it's the phone access or the "among other things" that you refer to, which I assume means other kinds of aid, training, and support, that provides most of the value in them finding a job.
Not that I know the answer, but I would have to see a source on this. Why would a device that may increase access to job postings, but a non-homeless job candidate is much more likely to have than a homeless person, increase the chances of said homeless person in getting a job? I'm not even sure that the ability to access job postings is the main problem there.
I'm not saying you need a FitBit for this, but if it enables this kind motivation in a convenient way, that could be well worth it.
I have nothing but sympathy for everyone involved and admiration for the strength of the parents. Few people are more motivated and capable than parents being told that a problem that affects their children cannot be solved.
Feature request for the calculator: if you say you have kids, it asks you what time they are in bed and asleep by and what time you try to go to bed: this window of time is now your chores/maintain relationship with spouse/gym/relax/hobbies/whatever time.
Is there new information here? No. But it's presented much differently from the official documentation and perhaps some beginners would find a guide like this less intimidating, more consumable, whatever - people have different learning styles. Maybe the people that would prefer this tutorial over another are a small minority, but I take issue with the sweeping statement that the work the OP put in here created no value for anyone at all.
This may sound silly, but before, when it was just me, without dependents, I didn't think as much about doomsday scenarios. Of course, I was still afraid of dying, but it just didn't cross my mind as much. After becoming a husband and a father, I started to (perhaps irrationally) worry about (a) not being there for my family or (b) the lives of the people I care so much about (when flying with my wife or kids). Fortunately flying is not a regular event for me, although I still do it when necessary (probably once or twice a year).
I can definitely see someone who has been in a founder role for years wanting to trade that for the stability, predictability and low-risk environment of a FAANG for a while, especially if they have a family, kids, etc.
Although a few exceptional people can do both, most founders sacrifice elements of their personal lives in order to put enough energy into their businesses. A "successful" founder can be a failure at home. It's not that you're absent, but you're also not the best partner/parent/friend that you can be during those periods. A stable, "boring" job can be an opportunity to dedicate more to those important things.