ndh2

I don't get it. The article doesn't explain anything. It's just a list of statements. "This is bad, that is good." But it doesn't explain why the bad things are bad, and how using monads is better. It also doesn't explain what monads are. "We note that lists are Monads." Why? How did you come to that conclusion?

My guess is that all the people praising this article already "got monads". But for the unenlightened, it doesn't do anything.

What is your role within the company?

Beware of the Halo effect [1]. For example, people are biased towards their first and last impression. That's why you/everyone should write stuff down regularly, so you can at least try to offer more objective and balanced feedback, and not just on the first thing that comes to mind.

I would recommend the book "Managing Humans", which originated from a blog [2]. It has good content on how to talk to people, and which mistakes to look out for. I found it quite entertaining. I believe you can read all content online.

[1] https://en.wikipedia.org/wiki/Halo_effect [2] http://randsinrepose.com/archives/youre-not-listening/

In my opinion the main benefit of code review is diffusion of knowledge. It's kind of pointless to let new hires do reviews.

Python has that as well: https://docs.python.org/3/library/doctest.html

> Some good experiences with C

> Reading the POV-Ray code source code for the first time and learning how to do object orientation and inheritance in C.

But https://github.com/POV-Ray/povray is all C++... It even says "Written in C++" on the Wikipedia page. Was he talking about some other source, maybe some older version?

Edit: [1] Here is a discussion about this topic from 2012. It seems that POV-Ray was ported to C++ for version 3.7.

[1] http://news.povray.org/povray.programming/thread/%3Cweb.4f01...

He didn't say at work though, he said in the office. Might have been after hours.

By the way: Props to dang for making all this possible. HN is very lucky to have him.

This is very good advice.

I would change the last point to: Don't work overtime unless you, personally, get something out of it. That something might be not getting fired. But if it doesn't get you anything... Don't do it.

Unfortunately 5. doesn't work if your company doesn't do any code reviews.

But who's forcing the Funny or Die guy to put content on Facebook?

I agree. I said that it was a mistake, but in the beginning it really wasn't. It's just not a viable long term strategy in my view.

I didn't say that.

It's not the 80s anymore, and the reason that C++ is still and will always remain hard to parse is... backwards compatibility.

Lots of posts here frame it like "Yes, it's a bit of a complex language, but the C++ committee has the difficult job of keeping everything backwards compatible, so it's understandable." But that's not the reality. The reality is that they (or Stroustroup) made that decision, and that decision was a mistake.

The correct way to deal with backwards compatibility issues is the way Go does it, namely to write tools to automatically upgrade code to a newer API [1]. And as that smug Google guy explained here [2], they have something like this for C++, too. They just don't bother sharing it with us peasants.

The fundamental mistake of C++ is to religiously keep backwards-compatibility with everything for all eternity. It's so easy to say that backwards-compatibility is a good thing. It's obvious! But ultimately that decision is the reason for all the problems that C++ has.

[1] https://golang.org/cmd/fix/

[2] https://www.youtube.com/watch?v=tISy7EJQPzI

I don't think it did. Maybe the terms are being used differently in different cultures. Nothing wrong with that. The article is written with an American audience in mind.

> most people would think

This is not the case at all here in Germany.

The article should be renamed to "Our transportation systems fails the seniors who neglected to build it".

There's a follow up email that has much more details. Not ELI5 though.

> But since the peanut gallery is paying lots of attention it's probably worth explaining it a little more for their benefit.

http://lkml.iu.edu/hypermail/linux/kernel/1801.2/05282.html

For some reason it really bothers me that they keep using the word "communist". Not an expert, but it seems wrong. Maybe socialist would be more fitting?

It doesn't matter what they use it for. They can use it all they want as long as they pay me for it.

I spent multiple hours on one assignment, only to have the guy tell me off in a 2 min email. Didn't even have the courtesy to give me a call and let me justify the decisions I made with the code.

If you want me to spend more than 30 minutes programming for you, that's called work, and I would like to get paid for that.

True. However, the discussion here in this thread doesn't indicate that everyone understood that statement.

Is everyone aware that this is merely a dump of "Stack Overflow Documentation" (not Stack Overflow Q/A), repackaged in PDF format ? (Also a request for bitcoin donations.)

https://meta.stackoverflow.com/questions/354217/sunsetting-d...

https://stackoverflow.com/documentation

https://archive.org/details/documentation-dump.7z

There is no indication that these books are curated or edited.

This depends a lot on what country you live in and whether or not you have children.

i18n = internationalization l10n = localization

Same here, I won't buy Titanfall as long as it requires Origin.

Just pick one from this list: https://en.wikipedia.org/wiki/List_of_Kim_Jong-il%27s_titles

This article is a bit of a let down. They repeat the same thing over and over again. That there are mothers who regret having children, and how they are criticized by some other people as soon as they voice those regrets.

What the article doesn't address is exactly why they regret having children, and what could be done to alleviate their problems. Or how mothers who regret having children differ from those who don't. Is it a personality trait, or does it have to do with the environment? Probably mostly the latter, but in what way exactly?

The topic is interesting, the article not so much.

Why do you like it? What do you use it for?

> C-like expression parser

What does that mean? What can you do with that?

> Source code view

Does it understand programming languages? Can you inspect the contents of variables like in VS?

My impression is that the focus is on debugging executables where source level access is unavailable. Cracking, reverse engineering. Are there people who use it for development?

Some facts in the article that was linked are definitely not correct. Fogbugz was out there before JIRA. Spolsky wrote about JIRA multiple times, yet the article never mentions it.

So what is this site anyways? There's no About page, no contact, no ownership information, no author, nothing. Looks like an advertisement to me.