koja86

What exactly is the advantage given by PageRank today?

Been thinking about related topics recently (probably as a result of this wave on HN) and realized that despite I am still a young pup (30) my goals are not that different. Knowing that certain company is actively hiring older, more experienced folks I would take it as a sign of potentially very interesting workplace where experience is actually needed and office environment might be actually sane.

Good job and great tool. Thanks.

This might actually be an interesting metric in regards to project architecture and/or project management.

Totally agree that exponential model explanatory power is great.

This! So much this! (Unfortunately my single up-vote is not enough to help you sir.)

Unnecessary complexity is god-mother of all evil (premature optimization included). The goal is to use as simple (to understand and to maintain) means, code, idioms etc. as the problem you are solving allows. I know fancy stuff and I know when not to use it (i. e. almost always) and value simple robust code much more than fancy fragile crap.

Seems like more people are trying to solve easy problems by complex means than people trying to solve difficult problems by any means. Sad thing is by using unnecessary complex means even the simplest problem can be obscured beyond mental capacity of anyone. Welcome legacy spaghetti mess.

Damn, I wish I could unread yours so I could meet my daily duplicates quota.

DR.

Last time I checked their custom C++ parser was not able to get even some simple templates. Finally they ditched it in favor of clang. Way to go!

Are you willing to share your tricks publicly?

The only real issue was portability. On any given system you could do that already before C++11. Now C++ standard hides those implementation details below unified abstraction.

If interested check this SO answer. http://stackoverflow.com/a/6319356

I think this might be special case of more general and more important topic of software project (or basically any human operated project) spanning multiple generations. Knowledge transfer, continuity of ideas, experience sharing ... all that difficult stuff.

The Other Side of the Cloud Hype.

It was related to "Everyone on your team should be able to be working on multiple small changes/commits/whatever in parallel."

Regardless of what SRE actually means I guess it must start with Senior. I have yet to hear official definition of that word but self-reflection, realization of own limited abilities and means-to-an-end mentality are something I personally would consider a strong candidate. Awesome mindset sir!

Context switching also creates some overhead. YMMV as the time it takes to switch tasks IMHO depends on particular person, context scale and problem difficulty.

The trailer "was" hanging from the ceiling. http://kxan.com/2016/05/11/man-says-tesla-started-on-its-own...

Fortunately there are un-modified forks. Created one more just for evidence: https://github.com/koja/linux-3.4-sunxi

Might I dare to childishly call your handle suitable without you being offended?

In context of software development these books (and other works by same people) might be interesting. I have not read them all yet but have been recommended by a colleague. My perspective is defined by being a developer in circa 100 people company.

* The Mythical Man-Month by Fred Brooks https://en.wikipedia.org/wiki/The_Mythical_Man-Month

* Facts and fallacies of software engineering by Robert L. Glass https://en.wikipedia.org/wiki/Robert_L._Glass

* Lessons learned from 25 years of process improvement: The Rise and Fall of the NASA Software Engineering Laboratory https://www.cs.umd.edu/users/basili/publications/proceedings...

By using relase designation instead of toy codenames ("testing" instead of "Stretch") in apt config files I get pretty close to rolling realease. Using that and apt-pinning I am totally happy running stable/testing/unstable/experimental system with majority of packages from testing on my desktop. I am rather conservative and would avoid anything bleeding-edge on production systems so using stable with security updates (and stable-backports if needed) would be my choice. YMMV though.

Maybe one day science can.

C++ developer here. IMHO the easiest access to quality information are books (usually not for free) but apart from that I was always able to find everything on-line -standard draft, language changes proposals, references, SO questions, blogs, talks, OSS projects, OS/hw specifications - you name it. Do you mean anything in particular you were not able to find?

Shit happens.

-Wall -Wextra -Werror -pedantic

"Second, because if you write good code chances are that the product you are building will be much better."

If "better" means anything related to user experience, adoption or commercial success I think that correlation is about zero. Even the dumbest idea can be implemented by good code.

It might look entirely different if you take social pressure into account as well.

Quote from TFA:

"I think that it's really important that the people who are doing free software and peer review can do vetting and ensure that things are backdoored."

[ insert generic remark about journalists competence here ]

Mea culpa. Thanks.

So it had to be found again: https://news.ycombinator.com/item?id=8335217

<spoiler-alert> Bug in question 4. Hint: count you parentheses.