skysight-inc/HackerNews huggingface dataset:
Projects die all the time. Even languages can (mostly) die. The death of a project is a valid part of a project lifecycle and knowing how it dies can affect how you deal with previous project phases.

Agile never assumes project death is a reality. It philosophically implies that you can always measure and iterate your way to the next phase... but that's just not true. No one measures and iterates their way to a dead state on purpose and yet, projects end up there all the time.

So how are the projects getting there and what is Agile doing about it? And don't give me the Agile vs. "Agile" argument. Assume a flawless execution of agile principles with completely accurate measurements and successful iterations took place when answering that question.

To me, agile just assumes infalsifiability because it refuses to acknowledge, let alone, prepare for project death. And worse, according you agile, you can even measure and iterate your way out of the grave.

The operation of a projects has more in common with biology than immortality. Treating projects like immortals flies in the face of the reality of project lifecycles and it brings very bad mental states to problem solving. It makes far more sense to treat a project in lifecycle phases (birth, child, youth, adult, mature, elderly, dead) than assuming a singular monolithic philosophy that completely ignores the arc of a project.

A: "The code base is too unwieldy, no one understands it any more"

B: "Oh, just measure and iterate"

A: "But that just creates more unwieldy code!"

Agile makes sense as a subphase of a project lifecycle for when that lifecycle is spinning its wheels in the mud, not as a end-all-be-all philosophy.

TL;DR: Agile should used if a project stalls, not as a guiding philosophy.
There's always lots of text flying by on the console; it might not be traceable to one single slow part.
In the quote, O(2n) and O(n6) are meant to be O(2^n) and O(n^6), right?
15 years in software development

- I'd quit my first job earlier. I stayed there for 10 years - should have left at 5. Things went gradually downhill after that.

- Spend more time building longer-lasting projects. I kept doing freelance work on the side for quick and small amount of money instead of using my free time to develop something that would benefit me in the long-term. I can't even remember those freelance projects.
I would have made a case with my parents for pursuing either a Computer Engineering or a Computer Science degree, and graduated with one, no matter how many years it would have taken.

I would have also pushed them further to purchase even a mid-range machine to learn all this on, despite our financial difficulties back then.

If I made these decisions early on, I know I would have taken a different path. At least, it wouldn't be the mess I'm in now.
Big IT Rising: Lean, Agile and DevOps
He's certainly unlikeable. I wonder if it's possible to separate the two: likability and charisma. I imagine there is a halo effect feedback loop for the two.
Thank you for that list! Would you mind elaborating more on why you'd exchange W-2 work for 1099 work?
First autonomous robot to operate on soft tissue outdoes human surgeons
Maybe the difference is that holding a bow is a physical skill? Once physical skills become second nature it's harder to unlearn them.
It depends.

Much like most "scrum" teams don't really do by-the-book Scrum, it was very rare to do by-the-book waterfall.

If you defined waterfall to mean

- get every requirement written up in absolute detail before you do any design

- finish the design in great details before you write any code

- if the design process identifies problems with the requirements (missing/ambiguous/etc), then stop the design work and go back to requirements phase

- write all the code before you start testing.

- if during development you find an issue with the design, stop development and go back to design

etc

Then I never saw any project that worked that way.

But it was quite common to have a requirements gathering exercise, write up a document that covered the requirements, get that "signed off", then do a multi-stage design phase (usually we'd start that before requirements were signed off, since the probability of the requirements being rejected in their entirety was pretty low), sign that off, and then move into development to implement that design. And then test the whole thing at the end once it was "done".

If at any stage we found missing requirements, that would get raised as a scope change. If, during development, we found that the design was broken in some way, we'd have a design change (which was usually lightweight and was a couple of emails saying "we can't do X, so we're doing Y, OK?")
That's very interesting. It may indeed be incorrect but it is what my priest taught, it is what my teacher at Catholic school taught, and it is what the retreat I had to go on to get married in the church taught.
That wouldn't really make sense at all.

Can you name any commands or interfaces that take the variable before the argument?
Right, the HMAC based approach is what is recommended over the bearer token approach. But you still leak everything else in the request.

Actually, the same logic should be done for cookies. You COULD replace cookies (which are bearer tokens) with signing every request to the server, but then you're just avoiding the REAL solution: https!

Actually the biggest security theater I have seen on the web is httponly cookies to "mitigate XSS". As if the main thing an attacker will do once they inject JS is to send your cookies somewhere. They can just execute anything in the context of your session while they still have it! So by being security theater, httponly cookies are worse than useless. The right way is to prevent XSS by escaping everything properly.
And buro9 retracts the main critical point later in that thread when several people highlight Google Takeout.
That is a very interesting idea. I paid for university via a hitch in a line unit, and while it's not for everybody, I would not appreciate anybody telling me I couldn't do it. In my case it paid off rather well.
I meant three families, but you still may be right.
I'm about two weeks from graduating with my bachelors degree in university. I'm 25. If I could change anything, I would have gotten more focused on attending university sooner so I could finish sooner. I'm not disappointed in myself, but I would have at least given myself three more years.
I'm in a state that honors broad non-competes and invention clauses and it is virtually impossible to find a software engineering job without one attached to it.

1099 work would give me more freedom to pursue other tasks while still doing work for other companies.

Also, you can't tell a contractor what hours to work. So I would have more leverage to set my own hours.

Edit: if I was in a state where non-competes were generally unenforceable it would probably be a different story.
There's a lot of city-living worship here. But (as would certainly be the case with myself) it's mostly for a very tiny number of mostly coastal cities.
These are mainly the administrators (read clerks) who are in the charge of the funding purse(s). You can contact them via your senators and other elected members.

Tell your representatives the following: The clerks that you have put in charge of funding our tax-money-filled purses for scientific research are just a bunch of uneducated or worse yet ill-educated fellows who do not understand even an iota of academics especially in the STEM areas. So they just rely on a bunch of very coarse proxy numbers (e.g. shitty impact factors) to decide funding. So please remove these clerks from these positions. We can and must install a better and more open system for reviewing where well known scientists/academicians can be invited to participate in the decision making process. Open access journals is one such great way to start. See what is being done by great academicians like Prof. Sir Timothy Gowers and Prof. Donald Knuth are doing for this cause [1], [2]. You may contact these people and get their advice in this matter.

Signed.

Your fellow citizen, a concerned taxpayer and a voter of USA.

[1] https://en.wikipedia.org/wiki/Timothy_Gowers#Elsevier_boycot...

[2] http://thecostofknowledge.com/#list
I think this isn't that FP languages themselves are not good for programming games, but that the languages don't really bring much more to the table.

Even when writing games in C, you end up writing many things in a very functional way by default. You have some state variables, and on every tick you advance things around in a very defined fashion, and redraw the screen.

The "default" pattern for making games is so close to functional languages already that the only thing moving to purely functional languages gives you is a tutorial on State monads.

In a way, this is a way of saying that functional languages are good for games, though...

meanwhile, OOP-style tools are extremely useful in games, because you often find yourself working with Entities with a lot of shared behaviour. The abstraction maps well to the concrete structure of a game.

Going to an FP-language will often cause you to sacrifice many OOP-centric language niceties without bringing much to the table to replace those niceties. In game programming, I think the tradeoff is much harder to justify than in other domains.
Practically, I can't see a reason either. But I imagine it would gain popularity by virtue of the Google brand and marketing.
Show HN: I am proud of this and in love with templates
I would be happier if I spent less time on facebook. It is a drug for me.
/etc/init.d/<variable> <command>
The other critical parts still don't result in a 37% net margin as it's basically labor. Most of it is low-skilled labor that should have plenty competition. The peer reviews of specific fields is high-skilled labor with decent to uncommon competition depending on size of field.

My claim still applies even if those costs are factored in. A yearly fee should be enough to cover everything. Charging $10-30 per article and such is just profiteering.
systemd is slow on my embedded devices booting from flash too.
The article is referring to the tax Apple would have paid on that money back when it was earned, if they had reported it as US profit instead of reporting it as foreign profit.
Every top 5 song from 1958 to 2016
Can we do something about the clickbait title? This is Judge Rodney Gilstrap, of the East Texast Federal District Court, in Marshall, TX.

The story is good. In particular, it highlights how a small cascade of incentives can lead to a grossly perverted and corrupt result, from the USPTO's issueing of crap patents (with full impunity), the Eastern District's procedures, Rodney's actions, and a home-grown trolling industry.
His writing is gold but most impressively his boldness in the Era he lived in.
How exactly are you defining a "recognition of danger"?

I ask because I'm trying to grant the greatest possible latitude to generously interpreting your statement. And that, for me, is quite a stretch, given that I feel you are moving the goalposts in a very significant fashion with the modifier of "incorrectly attributed to the supernatural". To quite a seemingly intellectually and rationally dishonest degree.

I get the sense you are building your argumentative trenches behind your restatement of "correct attribution", which involves way too much application of modern knowledge (and forgiveness) to past errors.
I came to make the same point - but PHP itself is not directly the problem.

There are many, very popular Wordpress plugins that take hundreds of SQL queries just to render a landing page. 10 hits/sec legitimately is "DDoS" territory for many businesses running such things.
20 years professional experience, almost 25 years programming in general.

I would've attempted to build something cool instead of build stuff for other people. I realized very late in my career that there was more going on than the agency life - at one point I was even chasing the big agencies. I built fun little joke sites, but never attempted to build something that could've been a business. Reading "Founders at Work" really opened my eyes to what I could've done back in the day -- and while it's not too late, it definitely feels like I missed out on a lot of opportunities.
Ask YC: is Paul Graham still doing office hours with YC companies?
A few days ago, I asked if PG was still doing YC interviews (the right answer is no).

When he handled YC over to Sam Altman (in 2012) he said he would still be holding office hours with YC companies. Is that stil the case? If so, how often?
You cut the quote to change the meaning.

"Although I still have serious misgivings about the systemd upstream’s attitude, I’ve got to say I find the system rather refreshing and useful in practice."
Or just bring back the BeBox. :)

(Still got mine.)
Visual C++ is just the product name, it's branding. It has no functional meaning beyond that.

As for the standards, there's pretty good partial support for C++11/14/17. One fairly recent blog post by them has some tables. [1]

[1] https://blogs.msdn.microsoft.com/vcblog/2016/01/22/vs-2015-u...
I think it's a mistake to think you're going to find the magic "right path" for your life based on what others did or wish they had done. Everyone is different, and your own path will be based on your unique abilities and desires which are different from anyone else's.

Generically I would advise, research your options, make the best decisions you can, and don't look back. If you end up unhappy with something, change it. Always be ready to answer "what would it take to hire you away from what you're doing now" because you never know when the question will come.

26 years in computer technology and software, experience in academic large enterprise, mid-size business, and a couple of startups.
What's really illuminating about this article is that it reveals the myopic thinking of a statist. The only solutions proposed are a) increase taxes or b) change spending or c) reduce liabilities. Where is option d) reduce the cost of roads?
11 years as Web Developer. As they say, hindsight is 20/20.

1. I would have pushed myself to really harden my understanding of the languages and frameworks I've used over the years. I usually get a cursory understanding and then just dive in. I should have, and still need to, continue to read, learn and keep up with ongoing changes and new practices.

2. I'd learn to negotiate sooner. It's never "work" when you do what you love, but then - yeah it is and you should be paid what you're worth.

3. As someone else said, push myself to finish side projects. I doubt I have any real moneymakers lying around, but I also have hardly anything to show for 11 years of work as it's only been with 3 companies and more than 4 years of that was not consumer-facing work. I still want to put something out there that I can proudly show off and say - I made that.

4. I had an opportunity to move to California (was in the midwest at the time) at one point and do basic entry-level database stuff for a friend. I backed out because it was a huge change and I was scared and I had just come off being an IT director and probably wanted something higher paying. Going back, I think I'd probably take the shot and see what happened. As the kids these days say - YOLO

5. Contribute more to open source. Both to give something back and to try to cure my ever-present imposter syndrome.

6. Definitely dive into mobile sooner. I'm a developer, not a designer, but I still have to throw together sites now and again and even the mobile-friendly aspect of bootstrap evades me. Responsive? What? It looks good at 2560x1600!?

7. Finally - and perhaps most importantly - BACKUP, BACKUP, BACKUP! Lost all my user data on a ramen-profitable side business that I managed to get going before I ever got my first professional gig as a programmer. Host corrupted my database and didn't backup either. I can't even remember who it was now, but this was 2004/5. I will forever kick myself for that one.
25+ years as a programmer

The biggest regret I have is taking a string of 4 jobs that all sucked, and sucked the life out of my enjoyment of programming. I lost about 6 years to these shitty jobs and it left me demoralized and depressed. But then I took 1 year off, which did wonders for me, I suggest it for everyone at least once in your life.

I should have focused more on becoming an architect instead of a front-line programmer, so that I would have a higher-ranking position now. But I moved around too much, and every time had to keep proving myself, which stunted my career. There's a fine balance between moving around to get better experience, and sticking around to level up in rank.

That said, I still love programming to this day, and feel blessed that I got into this field that pays so well and gives me a lot of freedom to move around.
When Wellness Is a Dirty Word
Try "systemd-analyze plot >boot.svg" and it will produce a nice svg graph of how much time each step takes.
Those aren't variables though, you are referencing specific files.
And Bitcoins and Google, FB, Amazon, MS, Apple shares and SF real estate.
I much prefer the plain packaging because:

- The anime picture is embarrassing to receive in the mail / at work.

- The picture itself is kind of creepy, someone walking past my desk once even described it as 'rapey'.

- I can reuse the box.

- I am not 6.
6 years interning as a software engineer, 2 years as a PM at Microsoft, 3 years as engineer #10 at Palantir, 3 years at my own startup, 5 years working as a partner at YC

1. Work on products that other people would find useful, and then be sure to release it. Early in my career I was a contract software engineer for an agency. I was selling my time instead of making products that could be resold with zero marginal cost. I would have focused on making products sooner.

2. Either learn, or earn. The best jobs frankly are both. If you're learning, it's OK if you're not getting paid as well, and ideally it's not forever. If you're not, then you better be earning valuable equity at a company that matters. Investors get a portfolio but you only get one place to work, so it's even more important that you invest your time in a place that matters. I would probably not have worked at Microsoft knowing this. I wasn't earning or learning at the time.

3. For a while, I decided I wasn't going to code anymore. That was a mistake. Thank god I ended up picking up software engineering again. Don't ever stop coding, even for a fancy title like program manager. If a job has a fancy title, the job probably sucks. Writing software is very high leverage, and more meaningful than writing a lot of emails.
It's certainly possible - but there are other sham/placebo operations with no incision that work equally well too, such as this laser operation:

http://www.sciencedirect.com/science/article/pii/S0735109705...

>After completing the LV mapping procedure and deciding on the potential DMR treatment zones, the patients were randomized to placebo (mock procedure, 102 patients), low-dose (98 patients), or high-dose (98 patients) DMR treatment. If the patient was randomized to placebo, the laser (already in the room) was turned on but no further procedure was performed. If the patient was randomized to receive the Biosense DMR treatment, a laser catheter was introduced and advanced to the LV (left ventricle).

This sounds (not 100% sure) as if there was no incision at all in the placebo group.
Something more than a weekend splurge:

Turtle Geometry: The Computer as a Medium for Exploring Mathematics

http://www.amazon.com/Turtle-Geometry-Mathematics-Artificial...

...and I've not yet tried it, but netlogo sounds interesting.

https://ccl.northwestern.edu/netlogo/
Care to expand on why?
After 30 years in the Software Business I agree with many of the comments:

1. Build your own company early on if possible. Only way to really make money.

2. If you must work for others change jobs every 3-7 years. And take your equity with you. The company's success or failure will not depend on you. Really it won't. Companies by their very nature are designed not to depend on individuals.

3. Learn to manage people. Hard job - your success depends entirely on the success of others. Talk about uncomfortable.

4. VC investment is the not the only way to fund your company. VC need the next MS or Apple etc to exist. The chances of you pulling that off are equivalent to buying a lottery ticket. The chances of you creating a company that makes a small number of people an above average return is quite good. A VC will find that a waste of time and exit leaving you with nothing. VC ask you to do something they are unwilling to do. Invest all you capital in one risky venture.

5. Don't be greedy. Easier said than done. If you can get a couple million for part of your equity now and live modestly but comfortably - do it. Freedom is everything - anything more is gravy. If the company does in fact take off the small bit of equity leftover will pay off big anyway.

Good luck
You'd hope they'd point to an active fork but it's not looking hopeful.

https://github.com/dotse/PacketQ/network
Bootcamp grad here. Honestly, I don't think it really matters what bootcamp you go to. I think the defining factor for getting a job depends on what you did before the bootcamp. If you're a college dropout (like me) don't even think about it. However, if you've had a successful career in your field and want to make a switch, you should have no issue getting a job.

As far as the most respected bootcamps, based on who I've talked to I would say App Academy, Hack Reactor.
Honestly, I think it would have been really bizarre if something as unrelated to the central product as the design on the box, changed something as fundamental as retention of customers.
If I restarted mine knowing what I do now, I would have been honest about what I was passionate about with myself and went after that. I took a meandering road to return to what I loved doing when I was younger (programming, hacking, etc). I spent alot of time worrying what others thought of my choices and acting accordingly, instead of worrying what I thought of myself and acting accordingly. I've been working in software engineering/data science/data analysis for about 5 years.. before that, my career path of 8 years or so had little to do with math and computer oriented work, although I was interested in those things as a kid and teen.
Have you considered that the new box is too "generic" or "corporate?" (For lack of a better word)

In other words, the old box, while plain, adds a certain intimacy. It doesn't look like a huge multinational candy company sent it. The new box, though, looks basically like any other piece of Japanese media.
Bin Laden hanging out for years in the Pakistani equivalent of a McMansion in Falls Church should raise some pretty major suspicions of everyone involved.
Again?
googling site:ycombinator.com "radiation hormesis" gives 15 stories where this has been discussed.
He will not be sent back... the British loooove providing refuge t o dodgy characters. Even better if they have money, ill gotten or otherwise.

http://www.huffingtonpost.in/2015/06/15/lalit-modi-sushma-sw...
How about egrep, then?
I am with you. "What was your best career move?" Is probably a better question. But even then difficult to translate to other individuals / location / times.
From the looks of it, you're essentially doing tracking. Won't be long before your solution also gets blocked by an ad blocker.
I wonder what this will do to the strong ties between SAP and Microsoft.
Most Ordinary Americans in 2016 Are Richer Than Was John D. Rockefeller in 1916
I don't have an actual career (yet), but I've been programming as a hobby for a few years now. What I really wish is that I had never deleted some of my earlier projects. They weren't that great, but they weren't terrible. I regret getting rid of them, because they would have been nice additions to my limited portfolio.

I also wish I had gotten more involved in other projects early on, as my current interests and portfolio are pretty narrow in scope.