I’m not sure about the newer editions but the first edition exceeded all my expectations profoundly.
198 karma · joined October 14, 2016
I’m not sure about the newer editions but the first edition exceeded all my expectations profoundly.
There isn’t any panacea for scrubbing your data from these brokers. All the spam email, texts, calls, or even snail mail most of the time are coming from hydras like the real investors I mentioned, not large companies. Personally, I’m so sick of spam emails, smses, and calls that I’m just going to bite the bullet and start over by making an anonymous email/sms/voip service with Twilio (I did this professionally for 7 years) and put an end to it all.
Personally I feel that most users are already drowning in notifications, emails, badges, slack messages, ads, calls, etc that even if you did do an opt-in for notifications that most users would just ignore them since their attention is already too divided.
One thing to consider is not what your software should do but how it will really be used. The software I wrote was designed for sales teams to do marketing and communication but one day I discovered a bug that crippled the service, disabling most calls, while trying to fix an unrelated bug. This bug had been active for months, yet no users had reported it because they weren’t really using the software, in their minds they would rather not work at all and file false reports in the software to make it appear they had done their sales calls to meet their quotas. The bug was fixed but no measures were ever taken to fix the real bug which was the loop hole users were using to commit wage theft. The lesson here is that most users don’t want to use your software, their boss is making them and they hate their jobs. So why not focus on the real problem which is figuring out why your users hate their work and then fix that problem.
Every service is crazy about being “realtime” these days but imagine if git was realtime...cringy...yet more people do “real” collaboration with it than any other technology given the proposition that communication software such as slack isn’t really about collaboration at all. I’ve come to feel that if a software service feels they need notifications in order for it to work then they haven’t truly automated the problem they are solving. It’s like try/catch statements: 80% of the time the catch statements in practice are just //todo comments or log to an error table no one will ever read. So my last piece of advice is to think about notifications like catch clauses, meaning that if you do your job right then notifications shouldn’t be necessary at all.
My advice, drop raindrop before it drops your bookmarks.
Personally, I only make something when a problem becomes so annoying or time consuming, that I’m forced to make it. This is why you should always do things the hard way or manual way first before automating it and only then can you say “Wow, this could make money”.
Contrary to what others have mentioned, I advise against keeping a notebook on you at all times. You end up obsessing over things and overdeveloping the idea and much of it is wasted effort. If a concept for a project/idea you randomly think of is truly good, you’ll remember it, otherwise it wasn’t really that important. The exception to this rule is if if the scope of what you want to do or the problem is very large and requires tons of research, such as developing a new programming language or OS, etc, and not just an app or farming ads.
Overall, I would say to keep your process organic and invest more time in learning new things than you do on gambling on what may be half baked ideas. When I’m not sure what to build and have time to, I just buy a book on a subject I’m interested in, that has some overlap with the idea and but more so with what I’m interested in as an individual—-hell, maybe consider writing a book. Otherwise, be very experimental and conduct small hypothesis tests, starting with your largest to smallest, to make conclusions and _do_ keep a notebook of them. This is simply a matter of taking inventory of what assumptions/conjectures you have and either rejecting them or failing to. What I usually do is take an assumption and do the exact opposite; if, say, you wanted to make a new chat app, then write an essay on why making a new chat app is a bad idea and publish it. You’ll be surprised how much software out there is “broken by design”.
What you should look for in an employer is some one who does his job and lets you do your job with the same autonomy. What you should look for in a job is something you can automate easily away and move on to the next job, which may or may not be at the same company.
Eventually you'll find where you want to be, at the level you want to be, and with whom you enjoy working--maybe not even as a programmer. I used to think programming was an art, but it isn't, it's a means to and end. If low-code isn't the level you want to work at, then don't do it. I told my ex-boss "No" plenty of times and you're a professional whom has the power to do so as well. In the land of the blind, the one eye man is king.
1. Know the difference between reasoning and logic. Reasoning is like telling a story whereas logic is more like writing an axiomatic proof. Don't give in to reason, only logic will help you find the right answer. I call reasoning "scheming" when it's done in the context that the person doing it believes they are thinking logically but are just fooling themselves.
2. Shut the hell up! Stop your inner narrative in your life keeping you stuck in life and just observe the world around you. I find it helpful when I’m _doing_ something and not making progress to _not-do_ what I’m doing—it’s quite magical and isn’t what it sounds like. What I mean is you assume an indifferent mental state which frees up your brain's resources to take notice and inventory of details you and others missed about a problem.
3. Follow the path with heart! Is there a splinter in your mind but can't quite put your finger on it? Don't expect to find your life's purpose instantly, it takes time. The best advice I can give you is pursue what makes you the most curious, not what will make the most money. This is because things you are curious about take less energy to think and learn about.
4. Be compassionate, not passionate. What I mean by that is don't pursue "ideas" but pursue what makes you happy and others happy; be a buddha and end the cycle of suffering. All that matters in this world is happiness. If making money like Warren Buffett does makes you truly happy (but not for the money itself) then become a stock investor first, programmer second--you see what I'm saying? Too many programmers have paralysis when it comes to side project ideas because what they enjoy most is programming and they are already programmers, so shouldn't you be happy by now ;)
5. Be patient! Don't try to think of an idea, rather find a problem (which could just be a tedious task you do often) as a consumer, not a programmer, that really bothers you. Then, rather than make a complete product at first, do experiments first not by building a product but testing assumptions or hypotheses, doing a trial, and draw conclusions from what you learned. Over time, all those experiments will result in _learning_ which is the modus operandi of business.
6. Do your homework! Spend a good year at least researching all you can about the problem you are solving (unless you're just making a metoo app) and why it isn't solved yet, because you may find out for example the problem is intentional which means it can't be fixed, it is corrupt by design. You may discover a simpler way of solving the problem that incumbents were too fancy to notice. Treat your problem like it's a real conspiracy which forces you to think differently about the problem than others; rather than just being an engineering challenge, it becomes web of even deeper problems, and you may just find that your problem is just the tip of the iceberg.