skysight-inc/HackerNews huggingface dataset:
Architected software would be profitable in fewer scenarios if we (software developers) didn't maintain such a high barrier to entry. We design our tools for ourselves and other professional programmers so that we don't have to compete with non-professionals with a better sense of the requirements. We force people to come to us, to defer to our understanding of how much architecture is necessary. We make our codebases just easy enough for a pro developer and no easier, refactoring and simplifying only when it becomes painful for a pro developer, and no sooner. That way they have to keep us as gatekeepers to all code.

It's essentially like you only made building tools for cathedrals, and no tools for thatched stick homes, and you create a culture around always building a cathedral so no one really knows how to build a thatched home. Essentially, creating a market irregularity through cultural expectations about how serious software has to be and who is going to be writing it.

(The complaint people always make when I say this is that making software isn't easy, it's hard, and notices couldn't possibly build useful software. I would half agree: some software problems are hard, and require a grizzled developer and some hard planning. But much of software involves no difficult computer science problems, and is more about understanding requirements well enough to be able to assign them to the right basic programming primitive, or a handful of common libraries. This is the kind of code that we use cultural friction to keep inside Engineering, and build cathedral-style, even though it could be done in thatched-home style by notices, if we structured our codebases for that.)
The weaker sex
Would you prefer a wrong answer or no answer?
Agree. Definitely no cathedral.

And what about customizing a Spinner's font and background color and popupBackground color and putting a non-standard element at the top?

And the amount of time it took before Android got percentage based spacing in layouts?

And the fun of remembering what UI attribute-values like android:gravity="center_horizontal", android:layout_centerHorizontal="true" and android:layout_gravity="center" mean?

And the awkwardness of using non-standard typefaces and using things like the RecyclerView and it's weird Adapter?

And the fact that for some reason they used an XML element named "layout" when they implemented their data binding feature?

And the fact that some attribute names are camelCased while others are underscore_cased?

And the ease with which memory leaks are introduced by inadvertently closing around context instances because you need context instances all over the place because the Activity is a god object?

It's all so very ... not ... like ... a cathedral.
There are way too many dichotomies that are getting muddled in this discussion:

- hacky vs. beautiful
- professional vs. amateur
- waterfall-designed vs. evolving
- centralized control vs. consensus control
- crufty vs. well-maintained
- open-source vs. closed-source

With so many axes to argue about, we can project whatever we are feeling about software today onto this "cathedral/bazaar" debate. We may think we are having one discussion, but we're actually having six discussions (or more) at the same time.
which you could do with just about any stripped-down linux distro. Heck, in gentoo, you could build it all and deploy a pre-built/configured tarball extracted to the root directory on every client machine you controlled.

none of which you seek is exclusive to ChromeOS, except the default lack of native desktop apps.
That doesn't work when you can't predict what other tasks might interrupt you between now and date X

You can still take a probabilistic approach to tasks that might interrupt you.
Very cool to see a startup built on .NET and Azure sell for $3B!

Some additional info on tech stack:

https://tech.jet.com/blog/2016/02-05-jet-engine-built-2015/

http://hanselminutes.com/494/jetcom-scales-with-azure-f-and-...

Disclaimer: Microsoft employee, Nazgûl
I do believe that this N+1 - N captures the idea well.

One issue though: If the requirements have changed, that is not a good metrics.

i.e. We did that theme blue for Iphone, now people wants it to be green AND on windows. It's not necessarily technical debt, it's cancelling everything we've done to make something else entirely (even though it may seem superficially similar).

If the requirements and/or features for N+1 ignore or counter the requirements/features from N, it's not necessary technical debt, it might be you've just got no idea what you're coding and you're running in circle.
Reasons to NOT open up the code:
1> Loss of competitive advantage
2> Open source is not necessarily any safer (heartbleed bug ... )
3> If software for the pacemaker is allowed to be updated like that on a computer, someone will update it with buggy software that can cause adverse side effects. Who owns the liability in that case?
If you've ever gone on a weekend trip and found yourself three majors behind on Babel upon returning to work, you'll enjoy reading this piece.
FYI it is probably the same technology. The whois record for confirm.io references the same address as that is listed on the contact page of advancediddetection.com The Owner orgname is also listed as 'Advanced ID Detection'.
You forget that the American is working 50-60 hours, and only being paid for 40.

"Adults employed full time in the U.S. report working an average of 47 hours per week, almost a full workday longer than what a standard five-day, 9-to-5 schedule entails. In fact, half of all full-time workers indicate they typically work more than 40 hours, and nearly four in 10 say they work at least 50 hours."

https://www.washingtonpost.com/news/on-leadership/wp/2014/09...

http://money.cnn.com/2015/07/09/news/economy/americans-work-...

http://www.gallup.com/poll/175286/hour-workweek-actually-lon...
Sure this is about pacemakers, but cant we say something similar about the rest of our body?
>Having a gigabit internet connection means you can download any content from any server in the world at 1Gb/s, right? /s

Anecdotal, but bzr(1) has always run fairly slowly for me. I don't know much about it, so perhaps I'm doing something wrong, but I've never gotten it to download at more than a few KBps, when git(1) manages to hit my max download speed easily.
Define 'most phones' (Not being able to replace the battery is a problem in my world).

Buying a new (crappy, what do you expect for 50 Dollars?) phone because your perfectly working one isn't supported anymore is NOT satisfying and not a solution.

Windows XP is actually a very nice example. According to Wikipedia it came out in 2001 and got constant (you can complain about the quality or bring up other complaints) updates until 2014. It's rather amusing that you bring up Windows XP as a _counter argument_ to decent updates. Most phone manufacturers have a hard time updating their devices for 1.5 to 2 years, let alone 13.

I feel that you're a bit lost. You want to save a bit of money ($50 is your example) when you purchase a new device because if it's becoming vulnerable due to a crappy manufacturer/vendor you can always .. get a different one for the same price?

Ignoring that this doesn't make sense, you're also hurting the 'herd immunity'. This argument of yours is comparable to anti-vaccines discussions. "I want .." vs. "The general public would benefit if this would be the case". I know what Kirk and Spock would decide, but you're entitled to have a different opinion, of course.
Automatic Annotations
I actually can't produce this document. Google's contracts with OEMs are strictly confidential. Only some from way back in 2011 have leaked in their entirety. If you actually believe OEMs just get AOSP and get to do what you want, you don't know very much about Android.

Google gets to approve or veto every Android device every OEM sells. And that's just for starters. If you're an Android OEM that has access to the Play Store, Google has an incredible amount of control over your company.

These are the leaked 2011 MADA agreements, but the new ones are far more strict: https://oasis.sandstorm.io/shared/A9MKYwaMtKZ1p5xC5KQlknXDP4...
Very nice to read other people's observations! Thank you, everybody.

I saw silvery-white ball lightning from my 7th story window a few years ago. It swooped, turned sharply and touched down maybe 200 meters away. It was a very bright, constant light against a cloudless blue sky in the middle of the day, moving at a constant speed.

The best explanation I have for it is decay products of cosmic rays, resulting in plasma soliton. My estimate of the wattage and energy of its light output would mean it wasn't from a source in our solar system.

I would think that if the source wasn't our sun then events like these would be very easily seen at night, and that my Northern latitude's long dark winters would de-bias opportunities to observe.
Meanwhile if the source was our sun, then I would assume observations would correlate with sunspot activity.
> The bazaar meme advocated by Raymond, "Just hack it," as opposed to the carefully designed cathedrals

More like carefully designed procedures (not the software kind), meetings, and suit ties.

The waterfall process can be as technically deficient as you want it to be, just like agile.
It's the same problem with coding as it is with socializing. I find reading books about things instead of doing ultimately leads to nothing but anxiety and a warped sense of whatever you're exploring. If you stay in those sorts of books too much it will begin to warp your mind. Taken to the extreme you get communities like 4chan r9k and reddits theredpill that try to boil every interaction down into a transaction.

You have to be well equipped mentally and somewhat socially to not let things like this bend your head.
It doesn't matter whether the sets exist in some platonic sense if the axioms (e.g. of Peano Arithmetic) are consistent. Nobody has been able to show that they are inconsistent.
has to be
I went through a six-month period where I was working 80-120 hrs/week. All I did was eat quickly and sleep when not working.

This did permanent damage to my metabolism. Towards the end, my body temp was dropping close to 95 deg while sleeping, and a few times I had trouble waking up. Should've gone to the hospital; any lower and your body probably can't warm up on it's own. Ever since that time my normal temp is one degree lower than it was before, and I've struggled with slow and steady weight gain.

The project was a success, but I wouldn't say that I've had success as a result of that effort.
Rails itself is broken up into smaller packages, so you can only load parts of Rails if you want. Very few apps actually do. (and that's only like 8 of the 80)
This reads like a classic example of mathematical quackery. This same author also thinks calculus, which had been instrumental to all of modern science and technology, is flawed.

So far as I can see he never actually contends with the actual precise mathematical definitions of infinity, or of convergence in his calculus article.

While I can accept that mathematics may have some interesting foundational questions, the author has not developed an alternate solution that makes any predictions or provable statements that demonstrate an actual flaw in mathematics. It's all supposition and bullshittery.

This is little more than farcical nonsense.
Recurrent calamities, fires and earthquakes hit the Grand Bazaar. The first fire occurred in 1515; another in 1548.[9] Other fires ravaged the complex in 1588, 1618 (when the Bit Pazari was destroyed), 1645, 1652, 1658, 1660 (on that occasion the whole city was devastated), 1687, 1688 (great damage occurred to the Uzun Carsi) 1695, 1701.[14] The fire of 1701 was particularly fierce, forcing in 1730-31 Grand Vizier Nevşehirli Damad Ibrahim Pasha to rebuild several parts of the complex. In 1738 the Kizlar Aĝasi Beşir Ağa endowed the Fountain (still existing) near Mercan Kapi.

https://en.wikipedia.org/wiki/Grand_Bazaar,_Istanbul#History
App Store Simplified Screenshot Submission Process
The article says that to have quality, someone needs to be responsible for it.

Of course, the "Bazaar" included the project named "Linux," which does have a single person in charge. So "single person in charge (or not in charge)" isn't really what the bazaar is about.

More generally, the article laments the lack of quality in modern software. I don't think that's a problem of Cathedral vs Bazaar, though, since software designed top down with authority telling everyone what to do can be low quality (indeed, you can see this sort of thing happening in many scrum style companies).

Rather low quality software is a reflection of the skill of the people who built it.
I love how this article makes its reappearance on HN every two years...

https://news.ycombinator.com/item?id=4407188
https://news.ycombinator.com/item?id=8812724
It's amusing that this author so stridently criticizes mathematicians for not examining the soundness of their presuppositions, and meanwhile the entire article is based on the weak presupposition that mathematical entities can't be considered to exist independently. While that's a valid position to take, it's also perfectly valid to hold the opposite view, but the author seems to think that their position is fact rather than axiom.
Bandera personally did no such thing and ordered no such thing. Harry Truman personally killed more Japanese people with two bombs than whatever you are falsely attributing to Bandera personally here. Why not criticize apple pie and barbecue because of its association with America and hence with such genocide? It makes as much sense as commenting on Ukrainian flower crowns.

I think your comments here have spoken for themselves. Go find somewhere else to troll for pay.
Nothing so fortifies a friendship as a belief on the part of one friend that he is superior to the other.

Honoré de Balzac
By "gender specificity", do you mean the word itself, or the people targeted by the insult? Using the word "gato" to describe a woman would be nonsensical, and I don't think that a word predominantly being used to insult only one gender (such as "bastard") makes it any less of an insult.
And you seem to have converted to a tech that has yet to see the road. Come back when we have some actual labour data, not speculation. I've seen many automotive techs come (FI, antilocks, engine management, collision avoidance, onstar) each with warnings about diminished labor costs, warnings mostly from people who couldn't change their own brake pads. Yet little has changed.
I never realized sharpness was identity + Laplacian, but that absolutely makes sense. Thanks!
I think you'd really like Arch or Devuan. You seem to be progressing past Ubuntu.
As the other comments here have alluded,

a) a typo can run unintended code on your box

b) a bad/old/hacked project (correctly typed) can run unintended code on your box

c) both of the above conditions are considerably more severe because they can be triggered with near-zero friction (unlike a gemfile, which are manually pulled-down and code is run from a separate command. Gemfile results are also generally small enough (1-2 pages) that one can visually spot typos if you are monitoring the output

d) complex dependency systems can often turn into dependency hell

e) (IMHO) instantly-available dependencies potentially reduce a given programmer's likelihood to attempt to solve their problems with the language itself (i.e. don't use Cassandra when a Dictionary will do) ... the nodejs community seems especially susceptible to this

That's all I can think of right now...
Anyone who has ever had to use any of Oracle's products would not be surprised, in the slightest, that a person who thinks like is a leader in their corporate culture. Even without the Android lawsuit, I always go the feeling that this is the type of person was running that company.

Edit:
It's customary that if the article dates back to a previous year, to put that year in parenthesis at the end of the post title.
While mtier may have exaggerated the difficulty of updating from source, "...writing a 20 line script to get notified if the page is updated, that's enough [...] updates are trivial: update, re-compile, reboot" downplays the hassle a little too much. Your procedures are fine if you only have to update one machine, but they are inefficient when you have multiple machines to update. Furthermore, OpenBSD doesn't need a lot of RAM nor disk to run, but to compile is a different matter. This is not a problem (at least for i386 / amd64) for physical machines made in the last 15 years, but is a concern for VMs. IME, w/o X11, OpenBSD (i386 / amd64) runs fine w/ 64 MiB of RAM, but needs 512 MiB of RAM to compile (excluding X11) without swapping.

For my use case, I set up a dedicated builder VM, have it build a full release, then "upgrade" the other VMs with my local build. Although the installer only officially supports upgrading from version N to N+1, IME it seems to work for N -> N "upgrade" as well. This is workable and not too complicated, but it's definitely not trivial.

That said, to me mtier doesn't provide enough value, either. Prior to me setting up a dedicate builder, I probably would be interested, if they provide support past upstream's support period. 1.5 years is not "LTS" to me.
It's just an edge trigger - pretty much a modseq counter on the entire user (though we have plans to split it up into categories a little more so you know if it's just a calendar change or just an email arrival)
It's why I use OSX at home for anything non-work related, I want an integrated experience that just works, I don't want to be IT guy at home. No messing around with video card drivers, no figuring out why my printer chops off pieces of the page, no constant wifi or bluetooth crapouts, support for Adobe suite or popular digital audio workstation software.

At work I'm happy to use Linux, but I use it for things it's great at, such as simulating our prod environment, coding, etc, but at home I just don't want to think after a long ass day, I want to enjoy computing.
"You're such a pussy" or "Don't be a pussy" can definitely be used in a derogatory fashion, especially in groups in which social status is dominated by masculinity.

It can mean, for example, variations on "Don't be so timid", "Stop expressing your fears", and "Take more risks".

Indeed, I have heard "Don't be a bitch" be used in almost the exact same way.
It doesn't quite capture the high pitch voice that really accompanies that line...
Loss of competitive advantage

There's a competitive advantage in keeping pacemakers' source code proprietary?

Open source is not necessarily any safer (heartbleed bug ... )

It's a hell lot more amendable to inspection than proprietary software.
Developers can now just upload one set of screenshots for an app. Optionally, they can also upload one app preview per device family. This will definitely make the release process of apps a lot faster.
That's a very sensible requirement. It says in the docs exactly what they use it for. Not like they put in a bunch of other dependencies and some 3rd degree dependency pulled in a C compiler.
> despite many share references, most people are in environments which apply Scrum in a slightly different way

Exactly. In fact, the linked text is a prime example: it professes to address the "standard Scrum as described in the official guide", and then goes on to condemn the notion of story points. Now, I happen to agree with those story-points criticisms, but guess what: that official guide says nothing about story points at all! :o
Not the GP: Android is NOT open source in my world. It's a code drop. It's what Microsoft used to do, before they discovered GH. "You'll get what we did after the fact".

Yes. AOSP is available as 'open source'. As a giant code drop, as far as I can tell. And the steering party for Android is .. that Ad company.
Even 'Nexus devices' aren't able to boot using AOSP last time I checked (Nexus 7, the ~newer~ version), so that is really bullshit. It looks like "Have fun with our current state, and really - nothing will work on your devices anyway because you need a ton of binary blobs matching our kernel".

Android is about as close to open source in my world as .Net was via 'the reference source' a couple years ago. "Source available" vs. "Open Source".
Exactly, the question is...how to pay for the daycare. My son went to daycare. When I went to grad school, it was half my salary. Literally half. Thankfully I had the US GI Bill, otherwise I'd have been hosed. Dealing with the churn in society, and lets not argue semantics, if you're on welfare it's likely the skills you have don't meet the market needs. We need an education system that enables people to learn to fish, while giving them fish to survive/take care of their families. Right now, that system is slightly borked. Online education is awesome at providing access to many people, the problem is getting employers to recognize the value of the degrees/certificates that result. Some do, many don't. I totally get it, the quality is all over the place. Then again, so is the quality of in-person institutions.
I agree, I want to contribute to FOSS medical devices.
In this case, I don't think the distinction is really that important; I think checking if someone is single or in a relationship to target them with an ad is more intrusive than checking if they're in a group of a few dozen thousand people who are single and like cats.
But not everyone had the same amount of privileges. People in politics often had bigger apartments, for example. So if you wanted "more" in a communist state, you went into politics.
I almost spit out my drink. High barrier to entry? The barrier is lower than it ever has been. Any nut-job with a few weeks of training can make a shitty website with PHP or Node.js and have it instantly accessible to the most of the English-speaking world.

Most of the tools I see for software development seem to be organized around the needs of the bazaar (or thatched huts) not the needs of the cathedral. A million toy languages which might solve your problem well, but don't scale to a million users. Websites like GitLab and GitHub so you can share last week's 1 kloc project with collaborators. Libraries that do that one weird thing you need for your project, and nothing else.

By comparison, the cathedral builders (Google, Facebook, Apple, Microsoft, etc.) seem to be building a lot of their own tools. This includes programming languages, frameworks, build systems, version control, operating systems, and so many other things. They build their own stuff because the tools of the bazaar don't work quite well enough for cathedrals.
Got error 508 resource limit reached, then it came up after two tries.
Unfortunately, it's a black box made from nature that we have to reverse engineer.
Because complexity lets them keep their jobs for longer. :-)