An excellent tutorial for terminal based text editor from scratch: https://viewsourcecode.org/snaptoken/kilo/

There's also a Rust-native version: https://www.philippflenker.com/hecto/

Like, lots of resources and consequently failure to move from extensive to intensive growth mindset?

No, just bleak, cold, depressing, vast spaces that make you feel meaningless.

I’d also add https://www.vimgolf.com/ as very powerful way to improve vim skills.

“Code: The Hidden Language of Computer Hardware and Software” by Charles Petzold should be what you are looking for. Author describes computing from the very ground up, and in clean, approachable manner. https://en.wikipedia.org/wiki/Code:_The_Hidden_Language_of_C...

I think bus ticket collecting was chosen as an example by the author exactly because starting a company about it is ridiculous to think about. So we can discuss just inner interest in something without thinking about outer reward.

Hmm. It seems to me, that if you answer such a question, then you do not know who your users are. And this is not good for your startup. Because you have to know your users to be able to fix problems worth fixing. So try ask another question. Who are my users? And what actual problem I want to fix for them? Then, I think, you will be able to find a way to them.

Professional and educated guy will still be able to earn his money when he'll become a father, but it's not true for that professional and educated woman.

Saying this reinforces the double standard. Why can't he stay home while she wins the bread?

This is happening more and more nowadays, but a man in that position still has to defend himself against accusations of being a “girly man” and so forth.

Another way to put it - will a man be seen as (a) more or (b) less desirable to most women if he makes the following statement: “I’d like to marry a successful career woman, and when we have kids, I’d like to stay home and be the primary caretaker for the kids”?

To answer your question, clearly the answer is b. That is exactly the double standard as stated.

What I'm really trying to get at is that no one should be staying home full time while the other is at work all day.

Careers are a very personal thing. Having a child shouldn't be thought of as something you do for yourself. You are doing it for the child and the world. It is important to raise them right, but not at the cost of your future. With two parents, it shouldn't be that difficult to split the time across both.

That may sound wrong, but in reality, it takes a village to raise a child. Why should one person sacrifice the rest of their life?

I see your argument why shouldn't be that way, but I don't see there an argument that it in reality is this way, at least not for most women.

It may quite well take a village to raise a child, but in practice for most people there won't ba a village to do so; One person shouldn't have to sacrifice the rest of their life, but more likely than not one you will have to do that; and while I can agree that 'no one should be staying home full time while the other is at work all day' and Scandinavian countries have very nice results with such policies for both parents, in USA most people will be forced to choose between either that or poverty.

So, to answer the question, you're stating "clearly the answer should be b" ... but is the answer b in reality?

>clearly the answer should be b

I didn't say that it should be B, I'm saying that unfortunately it is B. I can guarantee few women in the US want to support a man. However, I think the inverse is making more ground. Meaning I think less men are interested in highly dependent women.

The leveling of the double standard is happening not by women accepting dependent men, but by men expecting an independent woman.

Ugh, I mistook 'clearly is B' to mean the complete opposite based on rest of the comment. Sorry.

Living and working in Sweden, I can say that men do take lots of parental leave, but not nearly as much as women.

I think about this a lot, but have not formed any convincing theoryas to why this is.

Marissa Mayer is confused.

Marissa Mayer, or her virtually uncredited ghost writer?

You might want to offer pub/sub API, and it just can't be done with REST because of it's statelessness.

You're not supposed to have session state - but the resources you are accessing are (of course) stateful. Why not set up your subscriptions explicitly as resources that can be manipulated through the API?

Will you still prefer desktop app if you get all its benefits with web app?

Because you really don't get all the benefits of a native app with a web app. It's getting better, the gap is closing, but it will be a while before web apps are an enjoyable an experience as a native app. I think Sparrow was actually a good proof point of that.

More than that - apps like Sparrow move the goalposts actually. It was such a superior to experience to even the best native clients of the day that it widened the gap between web and native once again.

What was so much better about it? I tried it and was unimpressed. Search was slower and worse than web, for one. That surprised me.

sometimes I'm surprised by this sort of thing, but then I remember that Google is INSANELY GOOD AT SEARCH and I stop being surprised when that plays out.

It seems that TDD is not the best approach to design such framework. When you expect your api change frequently on early stages, tests may be trhown away wery fast and be useless. So it's better to delay writing tests for time, when api becomes stable more or less. You need to know what to test before actually test.