skysight-inc/HackerNews huggingface dataset:
The net present value to a developer of dooming their current employer's current project by choosing an unsuitable technology which they could put on their resume to negotiate future salary (at a position they'll be moving to in, on average, months not years) is going to swamp betting on something boring but stable, completing the project, staying put and crossing their fingers for raises that outpace inflation.
Are you serious? If you're making the assertion here, it's on you to support it. Don't try to put the burden on others to disprove something you've shown zero evidence for, that's ridiculous.
> There is a lot Facebook can do, but they are not, because they are lazy.

Therefore they contract it out rather than automate it? Your comment makes no sense.
Creepy? How so?
How printing goes after prototyping all depends... Some people shop their prototypes to publishers, some get the game to a more advanced state before shopping it to publishers, others self publish, and still others release it as print&play. There are various companies that'll print small runs/single runs of nicer cards (sometimes indistinguishable from "pro" cards), and some of those companies will even manufacture other components too, like boards and gamepieces.

I've printed a few print&play games on sites like printerstudio.com and received some really nice cards. It's a bit pricier than you'd want if you were going to get it manufactured for sale, but for a nice copy or two of something you're never really going to get published, it can be worth it.

There are other tools for making homespun tabletop games (some of which have been mentioned in other comments here), but Squib is pretty much the best if you want functionality/customizability and can handle doing stuff in Ruby. If I didn't already know it pretty well, I'd probably use the OP's site, though. The main thing you want when prototyping is to iterate a lot, so the easier one of these programs is to use, the better. OP's site, being web-based, is definitely easy... no need to install, works wherever a web browser does (lots of game design programs are Windows only).
> I'm going to state a likely unpopular opinion now, and advocate that most typical SAAS / CRUD projects start with Rails, and build from there.

<3

Rails can get you very, very, far. While it's sexy appeal has faded, it's real beauty has shone. I can hop into most rails codebases and be productive in a few hours. I can come back to my own projects and still understand whats going on. I think that's huge. Sure there are newer things out there, but nothing beats rails for productivity or maintainability and overall developer happiness - tenants i hold in high regard.

Exploring new tech is great - doing it in production is asking for trouble of all sorts. If you want to build something that lasts for a long time, build it as boring as possible.
> it's a problem with bad designers doing the design

No, it's not.

A designer making that mistake isn't a signal s/he is a bad designer. I've worked with UI designers who range from good to excellent when it comes to design.

Thus, my overarching point which was that UX ≠ UI

and that UX shouldn't be co-opted by UI teams.
> That's why at many companies, whatever tools and languages allow you to get an MVP out the door before a competitor are not merely accepted but are often celebrated and lauded.

The linked article has some points I agree strongly with, but I disagree in its approach to tools. An MVP that's out the door as soon as possible is unlikely to have the sort of incidental complexity tech debt that kills projects. It can't, because the focus was on shipping.

A quick prototype for an MVP is great, get stuff out the door as soon as possible. If your app needs some javascript, write it however lets you get it out the door the quickest - if that means importing someone else's big framework, fine.

I think the secret is more akin to keep _your own code_ as minimal as possible. Your infrastructure and stack should respect the M part of MVP just as much as the product should.

Cause I rarely see true MVPs. I see "ok in order to scale to a million users in the first year, we're going to need x, y, and z on top of...". And then you're not just importing someone else's JS code and writing your business logic on top. Now you're building several systems that have to work together correctly even as they get modified independently in the future, and so in the process you're encoding a bunch of assumptions about your business that the MVP hasn't actually proved out yet! And that's tech debt of the deadly sort.

We're far away from having tools that will prevent a dev from building something overly complicated if they really really want to. Instead, we have to prevent it by always asking the hard questions "do we really need this right now" and not being afraid to look like the fun police.
I am legitimately interested in understanding the arguments that support a view of rising injustice. My understanding is that, historically, justice has been pretty abysmal, and as bad as it may be right now, I am not aware of when and how it was any better. It’s certainly plausible but in the arguments here it does seem like “things are bad now” is being conflated with “things were better before.”
What markets are blockchain-centric companies targeting in 2018?
Transfer pricing. It's the same for all big companies operating in Australia (and probably most other countries)

Of course there's nothing illegal about this and it's very difficult to really do something about it. The Australian Tax Office is struggling with this problem every day.
HUSBAND AND WIFE PLIES ROCK CHallENGE
Band Name Maker
I'm not sure what point you're making. Calling something 'perpetual violence' is fairly relative, I suppose. So we could quibble about that. But the point that society is substantially less violent than it was seems pretty clearly true.

I don't really understand what point you're trying to make about judicial effectiveness either.
> simplicity is now my goal.

Simplicity is a great tenant, I find myself often shooting for clarity a lot as well.
it's funny sometimes i read things or see things online and i can't begin to relate to the subject that wrote/created/said those things.

this is going to seem roundabout but bear with me.

here is a video of tourists lamenting the drowning of a zebra foal

https://www.youtube.com/watch?v=RAHysptvEfo

i can't fathom the subjecthood of the person wishing someone would interfere (this is a savannah in subsaharan africa presumably - there is no such thing as fair - it's a completely unintelligible notion). now it sounds like a young girl doing the lamenting so it makes sense that i can't relate.

now you internet person

>the fact that kids (and some adults apparently) don't think through such things is not some sort of admirable trait.

i can't fathom your subject that you so miss the point that it is exactly this childhood naivete that the op is commenting on. of course children don't think through such things - they're children! they have no sense of property or privacy (nor should they!). this is exactly what op is saying he misses.

besides that the sentence as written is essentially the negation of op's and so adds nothing. it doesn't suggest why it's important that no one intrude on your space, it doesn't explain why it's important for people to have private spaces, it doesn't explore anything. it's literally a no to a yes.

>I don't shake sign posts for fun because I've had to fix enough things in my life that I know how actions like that can weaken or destroy an object that most people consider very durable (or indestructible) and therefore would amount to vandalism for the sake of "fun".

you can choose to ascribe malice or mischief to everything that's the slightest destructive, you are free to do so, but you should at least for a moment consider whether conservation isn't the ultimate goal of life.
>the solution is to invest more fully in the process, giving meaning to your life through activities that have no terminal point

Are there such activities? Even the more process-oriented ones, lacking final conclusions, have terminal milestones. The juggler will eventually master 4 balls; the violinist Paganini, etc.
Being a craftsman is one of those never ending goals. You can always perfect them, or teach them to your kids.
Funny, my first thought was earthquake. Past experience obviously clouds initial judgements...
I’ve had this very cynical idea for a while now. And that is, the only way we will get governments to stop this nonsense is if we democratize the extreme tax evasion... ahem ahem.. sorry, “smart tax planning” that these companies take advantage of.

Perfect opportunity for the Stripe Atlas team :-)

If you make it so an individual can pay $50 a month and they get this full double Dutch Irish sandwich shell company crap setup for them, and millions of citizens start to get incomes this way and pay their “lawful amount” rather than their fair share, then governments will start to clamp down.

Because right now we (private citizens who pay 25-40% in income taxes) are powerless in convincing our governments to do something about this travesty.

Thoughts? Remember, as these companies say with their weasel words “we pay the full taxes we owe!” So it would be legal.
Well, sure keeping maps offline could allow the connection to not be constant but the maps would require very frequent updating since being out of date could have dangerous consequences, and the updating would be most easily done by network.

Edit: which is to say, maps aren't really secondary parts of current systems but more like "co-primary" parts. The cars aren't planning identify traffic lights where they don't expect them.
How to Be an Adult
The cities are where all the autonomous weapons of mass destruction are.
from my experience, consultants put more emphasis on job security than salaried employees when making decisions like this; while they are actually more likely to do resume driven development. When things go south, they jump ship.
If you imprison people (violent or non-violent or even innocent) you may get less measurable violence. But perhaps only if you exclude imprisonment from your definitions of violence.

That's one of the things ABCLAW is hinting at I think.

I don't think it is the case, but it's worth considering.
Sure, but the difference is that Google plans to make its solution default. Mozilla could have done that first, but it didn't.
It still applies. It applies to the weapons we use, how we treat prisoners, and how we treat the injured. Bad things happen, but please don't ever think your solider's are willfully bombing hospitals or killing civilians.
Have we had the conversation yet about the politeness of not trying to hunt down someone who quite apparently does not want to be found?

I feel that there's no value to trying to figure out his/her identity other than personal gain at his/her expense. It doesn't help us collectively.
Great piece. 1) The title might be "Incidental Complexity is Killing Software." 2) Typing speed of scripting languages is truly a HIGHLY deceptive metric. Server resources are not free, and unit testing is wasted on type checking which compilers do cheaper. 3) For different sad reasons, software organizations CANNOT manage to do cradle-to-grave resource planning and schedule assessments all the way through sales, training, help-desk and MRO. 4) Why software ENGINEERS fetishize tool and equipment purchases like consumers I'll never understand. The application wins are cool. The tools are tools. 5) The developer stovepipe desire to "have their part work" is another contributing pathology. Software delivery is a team marathon styled sport.
My very first thought as well, though if it is so, then I wish they should have mentioned that up front. Maybe they don't because of legal reasons? Bleh
I have no idea what this is all about. Anyone care to give a simple explanation?
Maybe for AMD GPUs, but getting consumer Nvidia GPUs working with VT-d on Nvidia's drivers is a little difficult. GPU passthrough is not something Nvidia wants to support on consumer GPUs.

Edit: s/very/a little/
Plenty of utility vans and pickups with service bodies have no rear visibility. They back up all the time.
Regarding point A:

How can you really date a person's writing style to be from pre-2010? Is there really a way to prove this? And why does that necessarily date the person writing it as a 35-50-year-old?
You shouldn't publish something like that without at least reaching out to the person for comment.
I don't buy it. Satoshi Nakamoto was most likely Hal Finney.

1) Finney lived in very close to Dorian Satoshi Nakamoto (who happened to be unrelated to Bitcoin) - it's possible that he used his name.

2) Finney was the first person to perform a bitcoin transaction with Satoshi Nakamoto

3) Satoshi Nakamoto stopped writing messages after Finney died

There are a few other reasons I'm forgetting, but the coincidences are too many.

Interestingly, Hal Finney had himself cryopreserved. He may have invented Bitcoin, to get resurrected 150 years later...
This is really confusing for me since you keep implying JavaScript is all we need for safe, secure, efficient, and/or low-TCB apps like this one parsing and rendering PDF's. Yet, you arent rewriting Firefox parsers and renderers in Javascript: you are using a new language with the properties I just named. Properties shared with safe C/Java/Ada subsets used in embedded but with even more safety added (borrow-checker). That's probably because you didnt trust Javascript to do the job efficienty, securely, and without leaks.

Now, you do in this thread if it involves a risky format attackers love. I dont. I think complex languages running in large apps increase attack surface. So, I still recommend strong sandboxing whatever parser/renderer one uses plus developers in security-focused projects (eg Qubes) using compilers or languages offering safety if having resources to spare. Everyone contributing a little gives us more building blocks over time.

And far as your other comment, there are always new ways to turn C code safe or secure being developed. C++ might also be able to use them via a C++ to C compiler but has stuff like SaferCPlusPlus to help. For C, options to attempt include Softbound+CETS, SAFEcode, Code Pointer Integrity, and dataflow integrity. At least three are FOSS with one I havent checked yet. So, they exist. They could also be in even better shape if security tool builders put more time in them.

All Im saying on this since you seem set on Javascript for efficient, secure apps. We arent going to agree on that premise.
Shaking a stop sign isn't vandalism.
> Taking a single family home off grid using slightly over sized solar and batteries is already cost competitive in most areas.

What areas? I've checked a few and it wasn't remotely close.

It starts being doable if you are willing to do things like load shed during the night - but I'm not. The goal would be for a zero impact on my lifestyle storage system (e.g. multiple days of storage for A/C use during cloudy/stormy weather, no 'no laundry days', etc.) and that simply isn't realistic yet.

I find this important since when I do go off-grid, I think it's immoral for me to expect the poorer folks who can't afford such equipment to subsidize my free battery by keeping an "emergency" backup connection like pretty much all "off grid" folks I personally know. Yes, it gets real cheap when you don't have to size for an expected worst-case - but that's not very interesting to me.

That said - some of the DIY hacker style projects are getting rather close. It's very tempting to start looking for a couple old Tesla battery packs and the like these days and go it alone. If that's the case, I expect within 5-10 years it will actually be doable commercially off the shelf.
A lot of straw manning in this thread. Personas can be a very useful way to characterize your product's users. There are other ways as well. Each have their pros and cons. Personas are great for deriving a small covering set of concrete user types that can be used to guide and sanity check your design choices. It allows you to gather a bunch of user requirement info once and package it in a reusable way such that you don't have to do new research for every new design choice that pops up.

Have a new new design question about user needs or motivations? Consult your personas.

If the personas don't answer the question? Do some additional research and expand your personas.

Personas not the right fit for the question? No problem, use another tool like classic functional user requirements for this question.

Personas for food ordering apps demonstrate the usefulness nicely. You want to know the preferences that segment your users like restaurant quality, cost, and healthy options as well as demographics like age and income. From this you can derive a few clusters, and ultimately personas. Useful ones like "Jeff, the young workaholic that needs dinner brought to the office each night" or "Tom and Sarah, parents trying to find decently healthy takeout options for their kids". Now you can ask questions like, "do we have enough healthy options that Tom and Sarah's kids will like?" and "do we have an easy way for Jeff to reorder weeknight meals? Do we need a subscription plan?" You can do similar things with other user research tools but personas are very natural and intuitive for many scenarios.
That's one route, but if you look at, say, western Europe, countries there largely have both much lower incarceration rates and lower homicide rates than the US.
The kill switch should simply be launching a rocket or emp at the infected autonomous vehicle.
Amen. I think the effects can be significantly lessened though under various circumstances:

- highly technical boss (understands that things might backfire)

- flat hierarchies (responsibility isn't delegated through layers...)

- reasonable work culture with nice people

But yeah, as an employee this is a question of luck, landing in the right place.
The Tom Tom app no longer has updates. They've moved to a new free app that limits it's usage to a set number of miles a month, with a subscription fee if you want unlimited miles.
Here is the related thread on the Git mailing list:

https://public-inbox.org/git/CAP8UFD0aKqT5YXJx9-MqeKCKhOVGxn...
It's been over a month for me. My case hasn't been touched, except for one automated "read the FAQ" update. Lost my ETH transaction.

Thousands are having the same issue (lack of support), based on Twitter alone.

Tweeting at the CEO is useless, unless you're someone famous.

The really sad part - with the amount of money they are making ($1B/yr), they should be able to handle support. It's only several categories (account verification, transfer delays, lost transactions) that can be easily parsed/routed, and even answered to, programmatically in 80% of cases.
I suggest making a popular post on HN.
I had to go here before I received any response from the company:
https://www.consumerfinance.gov/complaint/
WebRTC Electron Implementations are on
> I think over-engineering is just plain old incompetency in a different costume. Good guys successfully manage complexity, bad ones don't. The bad ones have just more options now.

I've felt alienated in some ways because of this, so i'm glad you put some light on it. I don't understand devs that so casually over-engineer or choose what's flashy for what works. I guess it's a matter of the tech mattering more than the product, and i've often held an inverse opinion.
I don't understand what you are saying. Can you possibly give a concrete example of software trying to replicate human judgement and wisdom and how that's unnecessary complexity?
> One barrier to entry is the actual cost of acquiring a vehicle. You can buy a lot of iPhones to hack on for the price of a Tesla.

Assuming you're just a random person and not a serious organization (which would have money to buy cars), can't you just get a job at an auto repair shop to fool around with their computer systems in the evening?
Really looking forward to getting stuck into this course. I’ve a background in fluid mechanics, in particular writing code (in Matlab but more recently with python) to identify structures in experimental and numerical data. In essence this is very similar to classical image analysis. Looking to machine learning seems a logical next step. I’ve been working through Andrew Ng’s course and while it is very good it suffers from fundamentalitis to a degree. However I do plan on completing Ng’s course first.
>"I have had several friends who built businesses in the crypto and finance space in the past 12 months..."

I am curious were these folks that came from the finance world? It seems like if you have good connections in finance there's a pretty easy path there from which to raise capital.
Couldn't agree more.

Not only we have old businesses being entirely automated, automation itself is also opening up completely new markets.

Software complexity is exploding probably at the same rate it's absorbing the complexity that used to be scattered around companies in a less formalized, less cost-efficient way, across people and processes, w/ all the challenges that this implies (communication, correctness, monitoring, maintenance, etc).
Datacol: Heroku User Experience in your cloud account within minutes
OK, so how long do you wait? How sure of a thing do we need? By that logic we wouldn't do anything. Do you think coal got started with a sure thing?

How is it we're more concerned with wasting some money than the possibility of catastrophic climate change? This is why the federal government should be more involved with combating climate change - nobody is willing to risk their money, or their power bill going up, even if it means essentially saving the world and/or our way of life.
I''m glad I'm not the only one! So many of my rescue projects have been untangling overly-complex solutions by making the tech stack far more boring so that the project can make the project itself more interesting.
> First, because the use of proxy wars is a defining feature of 20th century combat; war in Yugoslavia, Iraq, and Syria is directly linked to great-power conflict.

Great powers have interests in every war ever, but when Yugoslavia broke up, the USSR and in 1999 Russia were too weak to be considered equal adversaries.

In the early 90s the country fell apart and a tyrant started three wars ending in ethnic cleansing and genocide. When he started a fourth one in 1999, a short and by modern warfare limited campaign finally stopped him.
The root problem here is our hiring and interviewing system.

Imagine if interviewing rewarded "look I know all this stuff about writing simple functions in Stack X" less than "yes, the project shipped, and beat its deadline, because we decided to use library Y that the devs already knew even with the acknowledged pain points, instead of bringing a new technology in just for this project. We have some less-mission critical areas where we decided to experiment with new tech, but needed something predictable here."

Evaluating a senior dev based on junior-dev-esque implementation tasks instead of "does this person know how to avoid over-complicating our job?" is ludicrous. As an industry we interview to find "clever" people rather than "wise" people.
I'm a bit skeptical about your claim that apple hardware is well engineered. I think they pick aesthetics over function, to the point that functionality is compromised - leading to computers that overheat.

The result is they have a lot of problems with tin whiskers. Which is why you'll find about a billion forum threads about people baking their macs in ovens, and similar hijinks.

Granted, if you're not using a mac for anything that intensively uses the hardware (for instance, just text editing) you'll never run into this problem.
Booting via kexec is the intended idea here. Theoretically, it should be possible to boot any other OS with kexec. We may have to test that assumption for this project...