vaskebjorn

My point was that what Nabokov said about Russian "When you speak Russian your mouth ought to distend laterally at the corners" also applied to German, and that saying "ich" properly in German was an example of this.

Yes, one does not NEED to have the mouth open wide to express the "voiceless palatal fricative" but if you do not do it with a "slight smile" as described in that video it will not sound right.

I truly hope you know something about German pronunciation, otherwise I don't know what would compel you to even comment on the thread.

Be born into a noble family with english speaking governesses.

Everything he says here also applies to german. For example, to actually say "ich" properly you need to have a wide kind of smile that feels incredibly strange to an english native speaker.

Yes it is very far from intuitive (as a developer I can tell when uis are designed solely by developers).

The way I think of it is this: you do all of your foreign language reading through the app. Lingq keeps track of which words you have seen: when a new one comes up it's highlighted in blue, when you define the word (mostly automatic) it turns yellow. Once you mark a word as known it is no longer highlighted.

There are SRS features built in, but I ignore them and just add words to anki when I feel like I need to.

If you love reading it's a really great way to get language exposure. Since looking up word definitions only requires a tap or click it enables you to read above your level (like reading with training wheels on). And just seeing a word over and over again in different contexts is a much better way to learn than hammering away at flash cards. The import from netflix/youtube stuff as I mentioned is great as well.

I also upload all of my own material (mostly ebooks) and ignore a lot of stuff they have there.

With eggs you are probably getting plenty of protein.

I have been mostly vegan for a while and I don't think my bike riding has been affected, but I can tell you it definitely affected me when it came to weight lifting. For the first time in my life I just wasn't improving at all from session to session (and this is in the early stages when you just start lifting again after time off when gains come easy).

I know there are vegan weightlifters out there but from what I know getting all of your protein requirements from plant-based protein powder is a big undertaking.

It's not enough to make me go back to animal products but definitely something I miss from my meat eating days.

I can second the Chartrand book (I believe you mean "Mathematical Proofs: A Transition to Advanced Mathematics"). I used this book in a "bridge" class and loved it; it really starts from first principles and gives you a lot of simple examples that you can build on.

In my experience writing getters and setters has been boilerplate 99% of the time.

But I still write them because situations arise where you do need to change the nature of that property, sometimes dynamically, and then it's suddenly worth it. You can, for instance, change a getter and none of the class's clients need to know or care about the change.

Though I haven't used Groovy much I like their approach to this: "Although the compiler creates the usual getter/setter logic, if you wish to do anything additional or different in those getters/setters, you’re free to still provide them, and the compiler will use your logic, instead of the default generated one."

> I know people will disagree, but a skilled photoshopper can often reproduce the look and feel of film with digital.

But why go through the hassle of photoshopping when you can just get the image out of the camera the way you want it? This is especially the case where you're taking a lot of pictures. All of that photoshopping would be tedious.

And why is a more "accurate" photo superior? Like take any famous photo and ask yourself: If the photo showed even more detail would it be better?

"The danger in trying to force object-oriented concepts onto a C base is to get an inconsistent construction, impairing the software development process and the quality of the resulting products. A hybrid approach yields hybrid quality. This is why serious reservations may be voiced about the object-oriented extensions of C described in chapter 20. To benefit from object-oriented techniques, one must use a consistent framework, and overcome the limitations of languages such as Fortran or C which regardless of their other characteristics -- were designed for entirely different purposes." Bertrand Meyer, Object-oriented Software Construction, 1988.

Yet another reason for this not already mentioned is that some enterprise customers actually expect these ugly interfaces. This horrible ie 6/7 aesthetic has come to signify what "enterprise" software looks like, and it's what's expected.