skysight-inc/HackerNews huggingface dataset:
I sort of understand what you mean. I've been in music production, more of a hobbyist, for the last decade and need to upgrade my hardware. Seirra doesn't seem like a great upgrade and Apple hardware seems like garbage. I'm shocked. My 2009 MBP is obsolete but then there's nothing for me to migrate to. I'd go 100% Linux if it wasn't for Logic and Photoshop + Illustrator.
Office developments often have "key tenants" that are big names that take an early lease on office space in a development and get a very good deal - having a big name then attracts other companies.

A bit anchor tenants for malls.
Like I've said the stuff that hasn't changed much is the CS, the actual engineering part has nothing to do with what we do today. 20 years ago the net was nowhere nearly as ubiquitous, hardware was incomparably slow, the bottlenecks were different - the focus shifted from single computer/mainframes/shared memory models -> distributed computing.

When I say copy paste in visual basic I'm talking about professional programmers that couldn't even abstract stuff in to functions but would copy paste shit all over the code - not copy-pasting from other sources.

As much as people like to bitch about our industry we have heavily increased engineering standard, if you don't use source control these days you get laughed at, if you don't use automated testing you're an amateur, even junior programmers know about patterns and nobody copy-pastes code over their code base - stuff like this was the exception back then not the norm as it is now. You can say MVC was invented in the 80s or w/e but up until maybe 10 years ago the internet was full of tutorials/guides on how to do web coding by interpolating PHP inside of your HTML, using string concatenation to build SQL queries and such nonsense. Sure top 10% never did that but the vast majority of programmers did and the broader industry has improved significantly since then, in no small part thanks to the frameworks that constrain the bad developers on to the "good path".
A Cane for the Blind That Senses Tall Obstacles
Yeah, debugging 2 bugs that are shadowing each other often takes several orders of magnitude longer to debug than just a single issue.
Right - I took the comment to be about working sane hours yields better results than working twice as long... and generally older folks are less inclined to work the 2x hours.
I love this quote from the article:

"The fact that millions of drivers productively drive cars without wearing a seatbelt isn’t a good argument for cars with no seat belt. Similarly, the fact that millions of JavaScript developers productively use an inherently unsafe language isn’t a good argument for the use of unsafe languages."
All new vehicles in the US have computer assisted traction control. For several years now. So a huge portion of drivers are already being assisted by a computer.

It was mandated because it improves safety. Automatic braking is scheduled to be a standard feature in the next 5-6 years.

https://en.wikipedia.org/wiki/Collision_avoidance_system

I'm happy to concede that these are sort of uninteresting in the context of autonomous vehicles, but they are very much computer systems that assist drivers.
The problem with that approach is that getting a high level VP position at a non-trivial sized company is pretty competitive and there are only so many open slots to go around. It also requires a strict career plan and the ability to play office politics very well, which I think most techies struggle with.

Being the guy who sells a small app, service, or utility on the side and clearing $150k a year, or more, via mostly passive income is a much easier trick to pull off. Also this approach can come with a sweetheart acquisition deal from a larger company that wants your product and can run in the millions, on top of what you've earned already.
San Francisco is a fantastic place, but I'm convinced that comments like this one that assume it's so much better than everywhere else that you'd have to be crazy to leave are evidence of a deep (probably not even conscious) need to justify the high cost of living.

If San Francisco didn't cost so much, people wouldn't feel the need to defend it in such ridiculous ways.
Do you mean to flash firmware onto the chips? The 68K was from a time where memory was all external. There's nothing on the part to "program" per se.
I2P + Tahoe-LAFS, IPFS
Redesigning the stomt sign up (mobile and desktop)
Too bad it prodyces buggier, suckier code.
Link to Slides here:

https://gotocon.com/dl/goto-chicago-2016/slides/MattRanney_W...

Any speculation as to why Uber doesn't just want to use something like Netflix Eureka / Hystrix instead?
I meant that the light bulb could tell the router "I'm IoT so assume I'm pretty dumb", to which information the router could respond in any number of ways. I don't think your setting would have the effect we want, however. The light bulbs have to talk to whatever is supposed to control them, so they have to be able to see the LAN.
At my company, we adore O365, but we looked at Yammer honestly didn't understand what it was for, and didn't understand why you'd want a social network at work for any company size, small or big.

What we actually needed? A logged chat that isn't inherently tied to any other service (ie, if O365 problems arise, we can discuss it, etc etc), and we tried HipChat early on and swapped it out for Slack.

Re: comments about Slack desktop clients being webviews... Slack seems to be much faster and use less RAM than Hipchat's desktop client which was also a webview. I can't tell Slack's desktop client is a webview tbh, even though I know it's one.

Slack also has that killer feature of knowing when you're not at your desktop and can interact with your phone in certain ways based on that knowledge.
Show HN: kenv – an environment file injector for Kubernetes resources
What Defects Can You Detect Automatically in Software Requirements
Things are not going so well for Marissa. She's a technical person and should have known better.
They used to be in both Cambridge and California, when they moved to CA only PG wrote this:

http://old.ycombinator.com/ycca.html
I've been programming in functional languages for twelve years and recognizably modern C++ for fifteen at this point. And yet, I'm not a graybeard; I'm 28. But what I learned at that point still informs what I do today. And it's why I respect that those graybeards' old work still has impact today.
> And the whole "we are cool, we configure in source code" is just lazy.

Right. A little config file parsing library does not harm (and can be just copied into the project) but goes a long way for user experience.

Look at icewm, one of my favourite software projects. Yes, it's written in 60K lines of C++, but it's rock solid, fast and flexible. The configuration mechanism is powerful and an example of "no bullshit" design.
Once the option for designer babies exists, wouldn't the invisible hand of the market start trying to impose this in a centralized fashion? Medical insurance (legitimately, IMO) tries to encourage you towards preventive care over reactive care. Once this technology is freely available, wouldn't insurance companies be more inclined to pay to make your baby a designer baby instead of paying for certain types of pediatric care that designer babies don't need?
The secret life of an Amazon reviewer
Ellipsis.js – Library to handle multiline ellipsis and complex DOM elements
Not only that, but this is important research, whether we have too many people in the adoption system or not. The success of the human species relies on pushing our boundaries, every bit as much as it relies on taking care of one another.
The stuff you learned in your CS course is still just as relevant as it was 20 years ago. The things you did in your development career are nowhere near so.

Did you use SCM, automated testing and design patterns 20 years ago ? If yes do you think this was the norm in the industry ?

I'm not saying those things are the only relevant things, I'm just pointing out the obvious examples of how much things have changed since then. I've said in another comment, we've moved from mainframe/single PC shared memory model in to distributed/cloud/networked computing in the last 20 years and the problems from that era are completely different to problems today. Even on the low-level end the basic design constraints such as the difference between CPU instruction speed/memory access/cache miss dramatically changed what it means to write optimized code, nobody these days rolls their own SQRT function to squeeze out a few extra CPU cycles, now days it's about making sure your memory is laid out so that you get as few cache misses as possible.
Nice site but it's very US-centric. Opportunities are available all around the world, why limit to only US states/cities (I have a whole bunch of jobs in Amsterdam that I could share if only it was possible!)
Well I disagree. It was written as a limited browser scripting language in 1992. I was never meant to be a full-blown development language. So, I guess that needed to be said ...
MacOS Sierra upgrade from a developer's perspective
Are formal methods and advanced static analysis used a lot in medical device software development?
I have to agree. I'm getting up there too. I'm the second oldest person at my current startup and I looked around yesterday and realized that I wasn't that much more valuable than the 23-26 year olds I work with. I think I'm a damn site more technical than they are, and I also think I manage my time better than they do, but I don't think I provide that much more value to the organization. Especially given the lengths to which they will go to burn through work (i.e. long hours and weekend work).

I personally think that 95% of organizations out there only need/want what the 23 year olds can provide.

I'm holding out hope though that when it comes to truly valuable and technically challenging work that more mid-level to large-ish companies still have teams that value the stability and vision more mature developers can offer. I think this is my last startup for a while.

I think this article hit the nail on the head. It takes a very mature and self-assured person to hire someone more qualified than they are and then hand over the commensurate freedom and responsibility along with it.
If you don't use source control these days, you're below average.

If you don't use automated testing, you are probably average.

Plenty of junior programmers know nothing about patterns except how to cargo-cult them.

Plenty of people copy-paste code everywhere.

I'm curious how long you've been doing this stuff, because this sounds like neophilia.
China’s Plan to Make the Yuan the World’s Go-To Currency
I was only considering doing it manually. I don't know how feasible it would be to automate the conversion process. The formatting and language used in these "edit script"-style bills varies considerably, as they are written for humans by humans with no standardisation.
Mac OS X is not BSD: https://wiki.freebsd.org/Myths
They are the ones who brought up non-programmers and that is why I accused them of being light on details.

I agree that point is preposterous, but it is their point.
> The stuff you did in software 20 years ago has absolutely nothing to do with the stuff that's being done today.

This is basically false in every way it's possible to be false.
Caveat: This is random advice from the internet.

1. If it were me, I'd start by installing Hadoop on a laptop since Googling indicates it's doable....for some definition of 'doable.' Even if I could not get it to work, reading the documentation and researching whatever problems I encountered would deepen my practical knowledge. Getting Hadoop up and running is also a facet in a practical working definition of 'knowing Hadoop.'

2. Linux Wireless driver BLOB's have been a source of pain for me. The work arounds for me have been:

a. Purchase well supported hardware, e.g. used Thinkpad and cards without obscure Broadcom chips.

b. Use an external wireless router and an ethernet cable. That's how I connect desktops and laptops around the office.

3. My gut is that the important knowledge for many positions requiring or preferring Hadoop will be more related to data science than technical expertise. On the other hand, looping back to my earlier advice, positions that are Hadoop first rather than data-science first will benefit from an operational understanding.

Lastly, what I've been hearing about the industry, is that 'embarrassingly parallel workloads that can take full advantage of Hadoop are not as common as was thought a few years ago. The big useful innovation of Hadoop is looking like the underlying Hadoop Distributed File System (HDFS) and other big data search/query tools are being built over it.

That's not to say Hadoop is dead or not worth exploring, particularly at the technical level of HDFS and in terms of applying data-science concepts. Learning Pig or Hive makes sense in service of learning how to apply data science concepts. Because Hive is based on SQL it is probably the more generalizable skill...and learning SQL is probably more useful than learning either in terms of employment.

Good luck.
What the cleaner saw: dirty secrets of the upper crust
if (false){
...buggy code here...
}
Building trust is one component, but it's equally important to explore whether you're compatible with your cofounder (or SO) across a wide range of emotions and circumstances. There are people I personally know pretty well who I trust but don't think I'm very compatible with. They might be great advisors or board members, but I wouldn't want them as a cofounder.

Like you said, in a constrained environment like the military, it might be possible to achieve this in a short period of time through deliberate actions. I'm not sure how much that approach would prepare potential cofounders, since they're going to be operating in a much more ambiguous and freeform environment.
Did I miss what WIWIK stands for ?
You can't have "Intelligent" without "Intelligent(ly sending over personal data to servers you don't own for fun and profit)" in your devices.

Because connecting your toaster and fridge over a local network, and running updates via your PC/laptop would be just too complex
That's a shame, I figure we need a few players trying to be different. The phone space has become so homogenised.

I had half an eye open for the next model in the Classic range, to switch from Android.

As my usage has changed the last few years, having a proper keyboard again is more appealing, along with less desire for a passive consumption tablet.
Seems like Microsoft is working on what you want, https://mspoweruser.com/microsoft-working-slack-competitor-s...
Jq: sed for JSON data
What's even more scary: you get the same litany of "reasons" explaining why people can't stop eating hot meals every day.

Comparing Facebook to alcohol/drug abuse is like comparing piracy to theft - it misrepresents both issues while making it more difficult to discuss their impact and ways to solve them.
> most production issues are caused by people

It's a well known fact, both for systems and networks.
This is incredible. Hiding a breach like this is bad enough but to not even forcing password resets should be criminal. I think we're living in an age where information security is still in the cowboy stage of things. I think we're due for some tough regulations here. Clearly businesses do not have our interests in mind and in these cases our interest will conflict with theirs.
With 800 services and 2000 programmers you already have a deployment problem.
BBM was their killer app for a while, but WhatsApp and the like have overtaken it. In addition they had their enterprise mail server that lots of businesses used.
> Even if the technology is close I don't think the safety will be as good as the "augmented human" model

Except allowing humans control is, by definition, less safe. Google's self-driving cars have had a total of 1 partially at-fault accident after 1.5 million miles of driving. While their accident rate is about the same as the average driver, what isn't the same is that humans caused all but 1 of the 17 accidents the cars have been involved in.

The software is well under 50 years out.
Hmmmm, Google et al. discover ᴍᴇᴛᴀꜰᴏɴᴛ¹.

Only 32 years too late...

¹https://news.ycombinator.com/item?id=12586416
Not really what the video addresses for the most part. Mostly talking about their development process and impact of breaking up their application into 1000s of microservices. This is more to handle their development team scaling, rate of change etc...
It can give something good like Google's Nexus, or something very poor depending on the manufacturer chosen
That statement is about the first code block; the second one as I commented is totally optional and I agree that it might not follow some code rules (;
What Entrepreneurs Need to Know About HR
> The stuff you did in software 20 years ago has absolutely nothing to do with the stuff that's being done today.

The longer I'm in software the more and more I find this not to be true. The stuff that has changed is all surface level. The underlying principles are the same. The skills needed are the same. The attention to detail and other attributes needed to get the job done is the same. The problems are basically recycled or scaled up versions of the problems we had years ago.
Yes. And they are required by the FDA:

http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidanc...

Therac-25 is an example of what can happen when medical devices are not held to a high standard:

https://en.wikipedia.org/wiki/Therac-25
What I wish I knew
When this happens there will be some American politicians claiming that Linux is communism, that open source is socialism and stupid things like "American pay for software" and other non-sense.

How do mitigate damage this causes before it gains any traction?
My guess (and it is just a guess) is that each of these services is made up of multiple even smaller libraries which are each being version controlled as a distinct entity. I'm not sure I could fully get behind working at that level of granularity, but it would explain how you end up with quite so many git repositories.
Just kill it in entirety already and move on to new things. Neither Android nor Apple is going to die in the forseeable future, so a BlackBerry operating system doesn't stand a chance.
All languages have types. Lisp, however, and particularly the versions that those people worked with, are dynamically typed, like Javascript. Unlike JS, they aren't weakly typed, but that's not the point. To say nothing of Ruby and Python, for which there are also programmers on that list.
While having tooling for tight debugging loops allows short release cycles, it leaves that decision up to the business
The interface really really needs search.
For what it's worth, the BlackBerry Priv is hands-down my favorite Android phone I've ever owned. It's a great product that deserved more success than it received.
OpenToonz 2D open-source animation software now available for Linux
Are you familiar with the Underhanded C Contest? It's possible to maliciously tamper with C code such that you definitely wouldn't spot it with a cursory glance over, and possibly even with careful study.
Fun tool – release pipeline generator
At 33, with over a decade of experience as a professional software engineer, I have no interest working for a team that values long hours over steady productivity, elegant solutions, and thoughtful architecture.

I know that plenty of companies have been built "quick and dirty", but honestly I think any company, regardless of size or stage, can benefit from someone with experience gained from building real applications.

I live in NYC, not the valley, so maybe attitudes are a little different here, but I have no trouble finding work at companies that value my experience.
I'm 41 and I still don't feel old even though I work with a few people who are 10-15 younger than me.

We tend to think of old programmers as these ancient neckbeards who write COBOL and FORTRAN and grew up on usenet programming PDP machines; but the reality is that 40+ year old programmers today were kids in the 90s, were in their 20s when languages like JS, Python and PHP became popular, and played quake 3 in their early twenties.

BTW I'm not doing straight-up programmer work, more of senior architect type roles in the past years, so it might be more "acceptable" in the industry to still be spending time with an IDE at my age in this context.
Looking at this site: http://www.abort73.com/abortion_facts/us_abortion_statistics...

there are ~1m abortions a year, 3.2% after 18 weeks; Which is about 32,000.

In absolute terms, this is dwarfed by pre-18wk abortions, more than half happen before week 8.

Hence it may be relatively rare, but:

a) The law allows late-stage, hence 100% of abortions are allowed to be late stage.

b) those figures might change, but in absolute and % terms. Early abortions are the more common now, no guarantees how that may change.

I think the many pro-lifers see the distinction as a slippery slope.
My experience is that a lot of the companies in the valley that are run by young people are very immature. The good companies hire a wide spectrum of experience levels.

"Reading between the lines," I think the original poster needs to be a bit more selective about where he applies.
Not sure I follow your orange juice / motor oil rebuttal but I'm going to focus on the more substantive portion of this interchange...

It's purely a misconception in the same way that 30% motor oil is pure orange juice -- which is to say, it's not a misconception, by my reading. I wonder what my IP laywer would say about it, will post if I decide to ask.

Unless I am looking at the wrong comment, @pluma's explanation is just that it's not a problem as long as you don't sue Facebook. But this is equivalent to saying that as long as you give up your only recourse in the event FB violates your IP, you'll be fine. To me it seems like a mentality that makes sense primarily if a person doesn't ever expect to do anything worth patenting, or doesn't ever plan on patenting for some other reason. Don't sell yourself short.
If you want long career in programming you should really do serious career planing during your 20s to make sure you check all important boxes: correct technologies, mix of different kind of companies, team sizes and roles. Otherwise you might get into complicated position down the road.

I am in the early 30s and on top of my ability, but I don't see my future too bright from here. 10 years ago I make decision to do freelancing and work strictly alone. It was blast, but once my stream dry out I don't think I will ever find actual job: guy in late 30s/early 40s with string of trivial or dead end projects for unknown companies, no experience working in team and such.

I am ok with it and I am having awesome time (and always had). Everybody just have to know on what career path they are and have plan B in their pocket.