In general, for complicated items, I prefer to code at one place and think at another place. They seems to require different parts of your brain, and have different 'comfortable spots'.
> The app or website should make my life better but instead it's harder.
This is the sub-goal, but not ultimate goal. The ultimate goal is to maximize the profit, with accounts created, all the analytics will work out, and they could do all kinds of promotions or targeted ads.
I guess that's the same reason why you are asked to install a mobile app whenever you visit Reddit mobile WEBSITE. It does not attempt to make your life better. At least it's not the ultimate goal of ecosystem.
> I know the immediate response to this is going to be "But America did such and such...". I don't care what America did. When someone is on trial for stealing a car, talking about how someone else stole a bike isn't a defense.
Well, this actually reminded me the case of Apple issued Microsoft for the infringement in 1988 [1], and Apple did not win because the Mac UI was actually 'referenced' from Xerox as well.
We recently converted a chrome extension into safari extension using the tool provided by apple [1]. While the conversion is smooth in general, the generated app (not the extension) got UI issue during extension review! Reviewer insists the app does not fit the UI guideline. I need to write back and explain the entire app is actually generated by the official Apple tool. The only use of generated app is open the preferences page of Safari. Anyway, after two back and forth, the extension is finally launched.
Oh, yes, Share point, the worst nightmare when I worked in a big corp years ago. I wonder if there are really some sort of experts that understand how does it supposed to work?
But, that's still better than 'trying to create a product that may solve the problem of others', right? I mean, feeling the pain seems a valid start point?
Actually even writing on wordpress.com is a bit too much, sometimes I just can't help but do the text decoration (font size, bold, underline). Nowadays, I write the blogs on the evernote first, it just makes your mind of writing more fluent. (Notepad also works, but you may lose the content accidentally.) Once you got the content, move it to a blog site and put down some cosmetics are just easiest tasks to do.
Yes, it works but not intuitive. I mean why use the checkout for the file reversion? And I think that's the problem of git: it's powerful and it works, but it's really not easy to get started.
Just some experiences of mine, I had been really stressful when trying to get a job, long time ago. And eventually I started the jogging at the time. To me, it's like sort of hedge, if I got my job later, I got a heathier body due to more work out. In other words, the destiny is not going to screw me up on both sides :)
Actually, I kept on jogging even after I got the job later, I don't know why but that does make you feel a bit better about life.
The article is actually useful, despite the annoying introduction line of `a few million poorer`. People could stop reading the article for whatever reasons.
> ... a while later I found out that the stress of completing all his other courses on top of his master's project had lead him to take the very bad decision of cheating on one of his exams. He'd been caught, expelled from the university, had his Visa revoked, and ultimately been kicked out of the country.
I figured it out in another incidence. I was in my first year as programmer, and I believed I was a pretty good one.
I remember I was hanging around in a small computer book store, and there was a big book of 'code complete 2' there. I have totally no idea what's that, just opened it out of interest, and I remember I flipped to a chapter about how to write a good 'if else'. And I was like 'holy crap, I wasted my entire life, I never thought in that way, I must be the rookiest rookie in the entire programmer world'. I immediately purchased the book, and that indeed helped me a huge deal in the career.
I think the paragraphs are simple enough, but my personal preferences is, some paragraphs better come first than others.
I am not sure if it's the same to others, but for me to learn a language for the first 15 minutes, I am really not interested with the differences of signed vs unsigned integers. I may have look of this when I got stuck somewhere later.
I think a better order will be:
1. play ground
2. hello world
3. control flow
4. function declaration
5. string, list and dict
6. featured stuff with this language (e.g. threading, async call)
I should be able to write basic stuff and play around with the above. Then I would try to sort out all kinds of remaining pitfalls myself :)