skysight-inc/HackerNews huggingface dataset:
These are really good observations. If there's a common thread, I would say it's the intolerance for failure exhibited by managers who don't understand software development. I'm not sure that intolerance would be lessened by another system, whether it be waterfall or kanban, or ad hoc. Prior to agile, when failure happened, it tended to happen in a big way near the end of the project. But if a project were two or three years long, as is common in software, everyone could move on to other jobs after having spent two or three years without having to report progress every day or demo features every two weeks. A couple years in one job is pretty typical nowadays. So in some ways it was a more comfortable environment for engineers.

Agile was introduced so that failure could be amortized and tracked. It makes the development process more transparent so that mid-course management corrections can be made and the corporate ship can be steered around the icebergs instead of running blindly dead into them. But in order for it to work, management must be tolerant of small failures. If it's not, then scrum will become theater with failure swept under the rug, and you'll be right back where we were, with failure becoming apparent only near product launch, when the iceberg suddenly appears out of the fog too late to avoid it.

Now, it may be a valid criticism that agile expects too much from management, that most software company managers aren't competent enough to use it. But that pretty much says we're all doomed anyway, regardless of what system (if any) is employed.

I'd be interested in your thoughts on why you feel kanban is better, since my impression is that it is essentially the same process but without sprint intervals.
We've been talking about this for over forty years now and it just hit me - engineers are categorized by what they build whereas software engineers are categorized by what they build with. If you asked an engineer who's an expert at building bridges to then build a skyscraper, they're likely to have estimates that are off-base. Meanwhile in the software world we say we're Java developers or Ruby developers or Haskell developers are whatever. The field is only now starting to really mature to the point where we can start categorizing different kinds of software projects and specializing in different practices.
Carciofi Alla Veneziana – Venetian Artichoke Hearts
can you elaborate on the second sentence?
Acidity is bad for teeth, particularly in locations without fluoridated municipal water. Is acidity implicated in any other health problems?
I really hope Apple reads that feedback form. Safari on iOS has a broken Content Security Policy for the font-src (namely 'self' isn't working) and I am getting flooded with false reports.

When I google it I only find an unanswered post on Stackoverflow:
http://stackoverflow.com/questions/29417735/content-security...

Do so few people use content security policy? How did this go unnoticed for so long?
Shouldn't that be "maître"? ;)
Job demand list by keywords
The list below shows the average job density index across top 60 most populous cities for searches at jobdensity.com
The JDI number represents the number of indeed.com job listings per 1,000 of population.
The job ad counts are pulled from indeed.com api.
The averages are bit misleading, because depending on the city and job terms, the JDI can easily go in to the double digits. I know it's not an apples-to-apples list, just dumped it for entertainment. have more data but HN limits post to 2,000 characters.

3.980-sales

3.570-software

3.514-design

3.385-veteran

2.911-senior

2.398-research

2.273-project manager

2.024-Operations Manager

1.756-engineer

1.722-driver

1.516-manager business systems

1.516-Nurse

1.512-data analysis

1.490-administrative

1.182-developer

1.050-software engineering

1.004-sql

0.958-Software engineer

0.934-programming

0.914-Data Science

0.885-human resources

0.872-business analyst

0.833-construction

0.788-c++

0.759-Facilities Manager

0.748-customer success manager

0.696-hardware

0.672-java

0.672-software developer

0.580-oracle

0.573-web developer

0.560-.net

0.548-JavaScript

0.540-Director of IT

0.505-'Chemical'

0.503-Chemical

0.496-linux

0.468-international program

0.454-"project manager"

0.452-computer programming

0.450-philosophy

0.443-control engineer

0.443-network engineer

0.425-therapist

0.407-remote

0.383-St. Louis

0.370-css

0.362-QA

0.330-Python

0.323-salesforce

0.321-facebook

0.314-Leadership Coach

0.299-Purchasing

0.298-user success

0.298-c%23

0.289-linux engineer

0.265-hardware engineer

0.259-Electrical engineer

0.255-accountant

0.252-pharmacy

0.251-mobile engineer

0.226-Sourcing

0.216-materials engineer

0.215-javascript engineer

0.198-mechanic

0.195-Ios

0.192-cashier

0.186-Scrum agile

0.185-ruby

0.185-perl
Mind.. struggling... to.. enumerate... security... implications...
I can easilty blame Apple for locking out functionality that underlying hardware supports though. Especially when it's essentially functionality handled by the hardware layer and drivers not written by Apple at all.
A Strange Loop (about Curtis Yarvin Being Kicked Out of Strange Loop)
I'd go with Facebook and the consequent support, testing and community over a framework that does it's own thing. Performance is simply not a concern for most applications (i.e. React itself is more than good enough) and having learned React to a good standard, I'm super excited about building something in React Native.
So I decided to search the definition of engineering on the internet because I've heard this whole "software engineering is not engineering" thing before:

> Engineering (from Latin ingenium, meaning "cleverness" and ingeniare, meaning "to contrive, devise") is the application of scientific, economic, social, and practical knowledge in order to invent, design, build, maintain, research, and improve structures, machines, devices, systems, materials and processes.

So, software "engineering" definitely involves the use of scientific, economic, social and practical knowledge to build, maintain, research, and improve devices, systems, and processes. So that, in my lowly opinion, makes it engineering "in the strictest sense of the term".

Arguing about semantics is extremely stupid if you are not a PHD in linguistics.
The "lizard people" thing seems hard to believe even at 4%. Maybe that's the number who answered that way on a poll because they thought it was hilarious? (Plus a few who actually believe that.) Checking your source now.
It's not C. It's a C-like language that he designed (and implemented) by himself. The embedded (rendered) resource references are my favorite part.
Similar idea for DC Metro here: https://github.com/bburky/git-dc-metro
Goblin Punch
Looks also the same as I was taught in the U.S. -- though I couldn't pull it off nowadays.

My grandfather grew up in the rural Midwest and wrote with a very attractive calligraphic style a bit closer to Spencerian; my dad still does too.
I think the biggest issue is you switched to using credits. That and you've only let this play out for 20 days. People can take quite a while to evaluate an app and decide to purchase. You have more experimenting to do. A one-time upgrade fee for unlimited or a yearly subscription seem like a better fit for how a user would expect to pay for this type of app than credits. At the very least perhaps add an "expensive" unlimited use option and I bet you get some purchases of that.
The Feynman lectures - http://www.feynmanlectures.caltech.edu/

For me it consistently produces one OMG or more per chapter.
ok yes, that too. But not all stocks do this, and the slice is usually incredibly small relative to the price of stock itself. Price swings of the stock will usually greatly eclipse the dividend.

Over long periods of time, however, dividends, when reinvested, do have a great effect.
Actually from what I read of the country facilitating apartheid with a brown face is not something I care to do

Its the same argument about working in pre Mandela South Africa.
Thank you! I can't believe I had to scroll almost to the bottom of the comments before someone picked up on the length issue.

To add to the already comprehensive list of reasons you gave for tram superiority - due to the electrical drivetrain and bogey system that all rail-based vehicles implement, there is generally more usable room for passengers inside the vehicle, as well as a much quieter environment due to the lack of engine noise. Additionally, the fact that light rail runs on, well, rails, means that generally speaking you enjoy a much more comfortable, smooth ride.
Nautilus Science News Quiz
"Software engineering estimates and plans often fail to live up to the reality that follows. It seems to be the only engineering discipline in which this is regularly the case."

Is it though? I live in Boston, home of the notorious* Big Dig[1]. While particularly egregious, it's far from the only large-scale civil engineering project that's gone off the rails. In fact, I'd argue that until fairly recently, many more public works projects shared the "surprise factor" of software projects. I'd recommend Caro's "The Power Broker"[2] for a fascinating history of NY-area public works (among other things - great book all around), including how much of that process was about adapting the plan to new things the builders were learning along the way ("oh, turns out that soil is completely different than we planned...")

That's not to say that there aren't particular features that make software engineering its own special snowflake - as there are meaningful differences between how civil, structural, mechanical, etc. engineers operate. But spend some time in another engineering organization and you'll find it's different, but not as different as you think it is.

(And FWIW, even civil engineers sometimes follow "agile" concepts - a company I once worked for was contracted to design a highway, and even after the construction started, engineers were "embedded" with the builders to make on-the-fly adjustments based on the environmental factors they discovered throughout the process... I wish I could find their project write-up, but it was a while ago and the company has long since been gobbled up by a bigger company).

* As a (subjective) kicker, I'd add that the Big Dig, over-time and over-budget as it was, was ultimately quite worth it... much like many software projects!

[1] http://en.wikipedia.org/wiki/Big_Dig

[2] http://www.amazon.com/The-Power-Broker-Robert-Moses/dp/03947...
As one senior former government official who once handled cyberissues for the administration, who would not speak on the record because it could endanger the person’s role on key advisory committees

In the commercial world, speaking out about security issues makes you a celebrity. In government, it makes you a liability.
Do you expect AutoRefactor to work with code using Lombok?

I did not try, but I don't expect so. Why? Because AFAIK, Lombok enabled code is not valid java code. So I don't expect that Eclipse JDT (basis for AutoRefactor) will be able to parse it. The only way to make this work would be to work on the code generated by Lombok, then do the round trip back to the original Lombok source.
Patch welcome!

If someone tries it out, I would be happy to read the feedback.

BTW I think AutoValue could work better thanks to the use of standard annotation pre processor.
Don’t Trade Time for Money
You might want to look up rhetorical question which was what my initial comment was.
South Koreans triumph in US robot challenge
Building a bridge of a million bricks - most of them do the same thing. A software project may have a million moving parts, all of them doing different things. The comparison is silly.

I'd use the original moonshot as a better example. It was hugely complex, unpredictable, late, had a large number of last-minute problems. They essentially used Kanban to solve it - hanging a drawing of the rocket on a large conference room wall, and taping notes to each place where there was a problem; reviewing each note at a 'scrum' meeting each morning.

So Engineering has been working this way for at least 50 years. There's nothing to see here folks; move along.
It's pretty nice, but you don't get two-way binding for free and it's not really baked in. In your example you'd have to use an input or content-editable element and then call ractive.observe and write your own code for binding user-input to your model data.

Compare to something like Knockout.js where you don't write any special code to get the two-way binding (other than creating each data field as an 'observable' field.)
US Air Force located an ISIS command by analyzing a selfie
'Queen bee syndrome' among women at work is a myth, study finds
I got an U2515H at work last week (for use with my MBP) and am amazed at the effect it's had on my working patterns in such a short space of time. Simply being able to have documentation, browser and editor open at once and not feel 'cramped' is amazing.
The pictures page is downright creepy
I got so excited when I saw the wall of text! I thought, "I will surely be entertained, for there must be some new crazy somewhere in there".

But I was wrong.

You are still going on about old crazy. You still think you can tell someone what their opinion should be, or that they shouldn't use phrases like "exponentially more complex" and "much more complex" without them being incorrectly and repeatedly accused of being contradictory.

And you still think that the confused folks in this thread understand the distinction between "local variable object references" and "the objects they reference", even though you yourself are referring to Solipsism's thread in which he does not understand that even after translating it to a language he is more familiar with?

Sorry mate. But don't despair, I'll give you one more shot. But bring some new crazy please, and shorten up your ramblings a bit.

Or I'm afraid I'm going to lose interest :(
If everyone did this (for cases where it actually mattered. Some app types are supported fine by in app ads) I would love to see how it would change the entire market perception towards paying for software. Right now it's viewed as a risk. A "should I make my app a paid for app or not?". I'd love to live in the utopia of developers simply being able to look at their creation, say that this is the value for it, and have people respect that.
...or in other words, a hat.
The reason that a program should strive to be unixlike is portability. The nice side effect is little bloat. Being unixlike is about the scope of a program rather than trying to make the implementation as basic as possible to the extent of not taking flags. If a program relies on another program to be useful, that's clearly not portable. It's no different if it's a library or another executable.

These cmdlets are excessively small in scope and that makes them intrinsically tied to one another. They're useless without their sibling cmdlets. In effect they're one giant program.

So I completely disagree that these are more unixlike.
Why not TOML?
One Night at a Restaurant
I would also respectfully submit the AT&T Long Lines Building aka 33 Thomas Street. A most intriguing looking building. https://en.wikipedia.org/wiki/33_Thomas_Street
Hofstadter - GEB - for sure

The Malazan Book of the Fallen (10 volumes) - Stephen Erikson - redefines impenetrable

Use of Weapons by Iain M Banks - master of the interwoven narrative
...and that breaks down so utterly when you consider inertia. Specifically, "bodies in motion tend to remain in motion". The math works, but the mental model doesn't. Almost nothing at the scales that need a quantum explanation can be adequately represented by monkeys who evolved to understand bananas. We can pretend to. We can give names to phenomena; call them particles and fields and so forth. We can make sense of the math. We can make accurate predictions. But when we really consider the implications of those things we claim to understand, we're forced to admit that we really don't understand them at all. It's turtles all the way down, and it turns out that the turtles aren't really there at all (for any reasonable definition of really).
You know as well as I that most programming reasoning is informal and doesn't have anything to do with any kind of proof.
> Do you expect AutoRefactor to work with code using Lombok?

No, I don't expect it to, but that doesn't mean I wouldn't like it to :)

> AFAIK, Lombok enabled code is not valid java code.

Lombok enabled code is valid Java syntax, as it is implemented as an annotation processor. However, Lombok enabled code won't type-check (or run properly) without actually running Lombok.
I've ridden on light rail - and the 'quiet' feature was noticeably lacking. It was rattling, clacking, whooshing, pitching, vibrating so loudly that conversation was impossible. Whilst a bus is generally pretty comfortable and convenient. So I don't agree on that point.
Wow, so, Hacker News... didn't see that coming.
Thanks for the comments, good and bad, folks.

One thing I certainly agree with: Regular physical engineering isn't entirely free of many of the problems I mention with software engineering, but the ability to understand and plan more effectively does appear to be there. The complexity in physical engineering does seem to be a little more tangible. I know a few civil and mechanical engineers, so I'm not plucking this from my behind ;-)

In terms of the definition of engineering, and the argument that software engineering isn't "engineering", I was taught this way back at university (City Uni, London), in their Centre for Software Reliability, and it's something I've largely agreed with. However, I think it was mainly used as a warning mechanism for newbie software "engineers" like me, to let us know that what we do is significantly different from other forms of engineering, in terms of the rigour. Perhaps it still deserves the title, but I guess that's a longer discussion.
Linux Kernel Interrupts and Interrupt Handling, Part 2
I'm perfectly capable, I just don't see the reason. Why should I install a JRE to run your program? The JRE has nothing to do with your program; it's incidental complexity. Go gives us a way to eliminate that incidental complexity and so is a step forward.
They're compliant with DP 1.1. The DP association doesn't require 1.2 be supported, although Apple really ought to. There's really not that much substance to the OP's hand waving here except for the fact that it's disappointing that there is driver support for the same hardware in Windows.
If you want Apple to fix issues report them through Radar: http://bugreporter.apple.com

They do get triaged by the engineering teams.
it's like a stripped down bootstrap? what am i missing here?
Book recommendation: Scarcity by Mullainathan and Shafir which discusses "scarcity traps" at length, esp. in the case of poverty, but also in other contexts (such as time scarcity for busy people, food scarcity for dieters, socialization scarcity for lonely people, etc.):

http://www.amazon.com/Scarcity-Science-Having-Defines-Lives/...
I totally agree. I put an app on Google Play Store recently with a yearly subscription based payment for use. Even though it has a 10 day free trial I have people downloading it, leaving one star reviews without even trying the app and leaving reviews with the likes of 'Should be free'.
Very disheartening..
You are still thinking too much!

I've known a bunch of let's say, less than savoury individuals. The average criminal doesn't plan much, crime is mostly opportunistic. They aren't typically thinking "this is theft vs. burglary and so I'll get a different sentence." They simply just don't think about getting caught in the first place and assume it won't happen.

The criminals who do think about what they are doing will aim for much more profitable behavior, such as targetting a number of homes or businesses all at once.
I think the Mods and the Zoot Suiters would probably win in the fashion stakes.
You are amazingly right. For all of the horrible things it is doing it does function pretty well.

On the biz side this might be a solution in search of a problem. I would go and ask my mailman (in person with the product, not show him the website) if such a product would be useful. If he/she said no (probably with some good reason) then it would be dead. Out in the rain or out in the desert/sun all day were my first two thoughts.
ls != list files in powershell.

ls is an alias for Get-ChildItem which is simply "get me a list of objects attached to the path". That's about as orthogonal as you can possibly muster.

It's actually more like plan 9 than unix.
If you don't insist on JSX, which you don't need, then just use react itself directly in coffeescript, and you won't be able to tell the difference without looking really close. The "canonical" description of this is at [0], but that page is kind of "old". I haven't found value in wrapping everything in parentheses like he recommends. Also that code is using renderComponent() which nowadays should be replaced by some combination of createClass(), createFactory(), and render().

[0] http://blog.vjeux.com/2013/javascript/react-coffeescript.htm...
Freedom by Jonathan Franzen
The effects of poverty on a child's IQ are at this point indisputable. (Duncan et al. 1998)

Chronically inadequate diet in the early stages of development will disrupt brain development. Missing meals will impair functioning and learning on the day of. These kids see reduced access to health services and often all around inadequate parenting from overworked and stressed guardians.

In ALL countries that have been studied, children with wealthy homes score higher on IQ tests than kids from poor homes (Case, Griffin, & Kelly; Keating & Hertzman, 1999). Also of interest is that in the US and developed countries in which the gap is widest, the differences in IQ is much larger than in countries with a smaller wealth gap.

Some kids overcome this challenge. They are the "resilient children" and their ability usually came from a shielding of negative influence through quality parenting or guardianship. Be careful not to absorb the narrative of these achieving kids and dismiss the very real effects of low SES on children.
> The user discounts the value of the free component to nothing and only measures the value of the additional functionality that is unlocked with buying the premium portion.

I think you could solve this by having two distinct websites, apps or even brands. It's not going to feel like a ripoff if they are perceived very differently from each other.
Having studied Software Engineering as a degree, I can assure you they teach software engineers the definition of "engineering", and stress that we are practicing something else or, at a stretch, an extension of engineering somewhat different from civil or mechanical. I realise that building projects probably suffer from many of the same weaknesses, but the degree of rigour, and ability to reason about the project, is definitely way higher than on software projects. I knew a few civil, mechanical and aeronautical engineers, and they tend to agree. That said, definitions like this can be hard to pin down!
>projects delivered precisely what they said they would, and in the timeframe they originally promised.

Those factors are "project management" which include concepts like "scope", "budget", and "critical path".

It's arguable if those are "engineering". They certainly affect engineering. (And likewise, some engineering constraints can feed back into project planning and feasibility.) In any case, project planning is a separate area of study. Using the author's strange definition of "engineering", it means the NASA Space Shuttle is "not really engineering" because it didn't deliver to the specifications of 50 launches per year at low cost.

A more reasonable definition of engineering that most could agree on would be, "the study (or art) of balancing technical tradeoffs against real-world constraints".