skysight-inc/HackerNews huggingface dataset:
I'm in the same boat as you. I have a moderately severe stutter that gets exponentially worse when I'm trying to sell my ideas to anyone. It sucks to have to swap words and not use the pitch you practiced in your head 100x times.

I don't recommend getting a partner solely to be the face of your company if your only concern is your speech. I recommend The McGuire Program. It is a 3 day intensive course that really helped me. It's not a silver bullet but in the end you will be comfortable speaking in high stress public speaking situations. I'm going to be attending their course in DC this year. Feel free to msg me if you have any questions.
In this discussion I very rarely see mentioned how heavy are cars. Since when do we need multi tons machine to move a being that is usually below 100kg from a to b? Here in northern China, many people have very small egg-cars, which are nothing more than an electric bike with a thin shell for the cold, and this is much less likely to kill someone by accident.

I think we have been under a very strong brain washing so that we all believe a nice car is big and has this and that. Maybe these car ads will be seen in 20 years the same way we see cigarette ads right now: dangerous brain washing by a lobby gone crazy.

(Edited slightly to avoid unfortunate pun)
ITYM Helium-3.
In my experience driving is much more interactive and not so much rule based in those cities. You have to judge other drivers - there aggression and willingness to drive into your lane, there willingness to let you sneak in in front of them.

Taking traffic from all sides into account might be something that works better for self-driving cars. Knowing when its ok to force someone else to slow down might be harder. I don't expect this to be just a question of scaling up. It will require new concepts and models. You might have to choose the country like you can now choose the language for predictive typing on your phone.
Let me switch this around and ask why have user names at all?

Most sites these days allow you to log in with your email address as your "username". At that point you should be able to choose whatever you want as your display name.

The only problem with getting rid of the username completely is that the username is by definition a unique string, while display names or real names can be the same, so you have an issue with deduplication of display names. You can easily end up with a system like YouTube comments where people troll by using the same name and avatar as others to impersonate them.
Can you contact me please? kiberstranier%gmail
The resurrection of the automatic watch
I've seen TDD used in the same way "teaching the test" is used. They say, "We've got 100% coverage! Our quality is high!" Meanwhile people are bitching left and right on Twitter about the product and there are deeper more endemic problems. It's just another form of scientism gone bad.

It has it's merits, but has it's negatives too. Blindly pretending there are only positives is disingenuous and a hallmark of scientism. I think that's all DHH was saying.
As a developer of commercial software, this strikes me as a lot of paranoia, although I do agree with one or two points.

These types of agreements have to be somewhat broadly written so that if someone acts like a jerk and e.g. resells Datomic as a cloud service, the license has a way to stop that. It has nothing to do with preventing you from privately installing your Datomic instance on AWS, or otherwise being a reasonable customer.

Companies generally have a strong interest in being fair to their customers. Taking the most paranoid reading of the license text like it is constitutional law and tyranny is right around the corner is simply incorrect and unfair.

I invite comment on my own license:
https://wukix.com/mocl-license-agreement
(for https://wukix.com/mocl)
Letting users pick up where they left off…without logging in (is this bad form?)
I'm really enjoying the posts on this article ... startup wankery meets the real life British commuter.
SDK for creating floating android application
I dropped out due to financial reasons, and personally I just don't list a degree next to the education. I have never had a problem, and if an employer asks I just explain. I think most HR folks interpret no degree listed as meaning that you attended the school, but did not get a degree.
It's not technically "self-cleaning" because it doesn't really clean itself but more dirt-repellant. Self-cleaning does look a lot better marketing wise though.
Let's say mildly that SOA failed and unfortunately the remaining parts are not "a lot". I was in fact able to understand them and it's been possible for me to open source the very most important parts in a POC. So the very most important part is the way message processing and transformation is done. IBM offers this in Message Broker / IBM Integration Bus (IIB) which they implement in c and I implemented it in Java. I called the project "use-the-tree" and open sourced it on github. A deployed version is online at www.use-the-tree.com.

Actually it turned out that I added a couple of improvements which makes my implementation superior to the one IBM has.

There are open source ESB's and Broker's, but I did not find (and I think it is unlikely that there are) comparable proper implementations.

Main areas of future work are:

- Add support for JSON
- Add all quirks that XML has
- Investigate if JavaScript (or Go) can be used (instead of Java) (and implement it)
- Sorting (super cleverly with tree map ofc)
- On-Demand Parser (would be awesome, also hard)
- Investigate on open source solutions for parsing flat files standards like EDI/EDIFACT or HL7/ORM formats and it's usability together with use-the-tree

There is constant change in the IT world (I see a decline of SOA and a push towards open source), so that I think that this project can have a significant success in the future. Again ... "use-the-tree" is the only thing which is left of SOA if you remove all the bad parts or the ones that have just failed... it is "SOA - the good parts" :). It provides strong guidance on how to do message transformation (to end up with the most efficient transformation code) as opposed to IBM's approach, which is "we provide you with every possibility and you better choose wisely".

Xslt would look like it, if xslt would be done properly.

I consider the way message transformation is done a defacto standard (there is "only one right way") and this is now open source :)
As a sometime cyclist, I agree that cyclists should abide by traffic laws. I assume this was downvoted for tone. The premise is undeniable. Bicycles should obey the laws. Greater rule adherence means a more predictable, and thus safer, street.
I'm writing a multiplayer game in Go. The reason I chose it is that it allows me to control memory layout at a low level. This can be very important for achieving multicore parallelism. (Also known as optimizing for fewer cache misses.)
You can actually purchase Rust-Oleum's NeverWet in stores now: http://www.rustoleum.com/en/product-catalog/consumer-brands/...

It's not perfect - limited lifetime etc., but there are ways around that (re-applying annually?).

In general though, the reason you haven't seen these much is that it just takes a while to get from the lab to market!
I suspect this would only work with men. I'm told that for women, every interaction with a random stranger could be the start of a physical assault. Then again, the author of the article is named Elizabeth, so I'm kinda confused.
The Hackaday Prize. You Build the Future. You Go to Space.
There has been some concerns about carbon nanotubes could have asbestos-like properties [1] if not handled properly.

Maybe that could be part of the reason?

[1] http://www.ucl.ac.uk/news/news-articles/0113/130115-chemistr...
I'm the author of the post, mine was sarcasm.

I wanted to explain two things:

1. A Design pattern or an opinion can be right for some people, wrong for other. There is no such thing as absolute truth.

2. Indirection in software development is a subjective matter. MVC can be fine for some people, not enough or overkilling for other. But argumenting things with "My solution works" or "I use it in my successful business" is nonsense.

That questionable Ruby snippet isn't something that I'd use for real.
You definitely follow different people from me. What I mostly see are links to interesting projects and gigantic social issues flamewars triggered by people overanalyzing each other's casual insights. For the former, it remains more than worth it.
It's more than just Chase being a judgemental prude here. Apparently, the US Department of Justice is threatening banks with fines if they don't shut down some accounts that are deemed "high risk", which are apparently mostly accounts from people involved in the porn business. Even totally stable and legitimate businesses.

The real problem here isn't so much that people are being unreasonable prudes, the real problem is that they're secretive about it. If they want to ban porn, they could simply propose a law to ban porn, and then send court orders demanding that banks shut down these accounts. But that's not what's happening here: the businesses are totally legal, yet unjust fines against banks are used to coerce banks to close those accounts without a sound legal reason to do so. It's a corruption of the justice system, and should worry anyone, whether or not they like porn.

(Disclaimer: I couldn't care less about porn, but I care a great deal about justice.)
After these essays and the scuttle on Twitter, to me this whole debate is not about TDD per se, it's about how far you take "architect for testing".

Purists like to create a pure in-memory application or domain model with no framework or external system dependencies, with adapter layers to isolate such dependencies. Some call this a "hexagonal" architecture, after an essay written by Alistair Cockburn, where your core code exposes ports to the various external hooks, whether a GUI, REST API, database, notification system, etc, and your TDD drives against these ports.

The benefit is that your core unit tests run very fast and allow you to move very quickly with the core code, and to refactor things quickly. The drawback is that your end-to-end integration and acceptance tests tend to be brittle since they often wind up being deferred to late in your iteration or release.

DHH on the other hand built a pretty popular set of patterns and frameworks (ActiveRecord and Rails), and really doesn't see any value with a codebase isolating itself from those things. Layers of indirection defeat the productivity benefits of these patterns and frameworks, and also give a false sense of comfort with the quality of end-to-end integration.

For example, to some, unit testing with a database in the mix is a no-no. To others, it's fine if you can make it fast and predictable (eg. Swapping in an In memory SQL store with test data). Another example is TDD from the UI through Selenium, Watir or Capybara.

Uncle Bob is saying actually he's fine with such dependencies if you can meet the speed and reliability targets of a pure model. And if you can deal with the coupling you've introduced.

To me, TDD is about whether you write your tests before your code, and that each test is isolated from other test contexts. As long as you setup and tear down your context quickly and reliably, you can include whatever dependencies that make sense as part of your daily development activities. Your level of coupling to a framework is a tradeoff of productivity today vs future proofing.

The clear "wrong way" practiced by some inexperienced TDDers is to not design a hexagonal architecture at all (ie. don't build clear APIs and SPIs and test outside in!) and to mock every external dependency, testing from the inside of your application out. This bakes implementation details into your test cases and makes everything brittle.
The burn would probably (deliberately) be done in such a way that the asteroid's trajectory would never intersect the earth just in case it failed.

Once it's in orbit around the moon it's not going anywhere.
Simple solution: Don't follow accounts that tweet content you don't like.

Twitter's great for following friends or people I respect in that it helps me feel a bit more connected to them. If you just want a list of most recently added content to a site like Huffington Post: Maybe consider using an RSS reader.
I agree, but you’re projecting; DHH hasn’t said anything that nuanced.

He doesn’t explicitly touch on “other desirable qualities” of designs (other than the meretricious goal of “clarity”), nor how they relate to testability. He just makes fun of testability without exploring what it means, how it can imply those qualities, and how to decide which tradeoffs to make.

That’s a shame, considering how many people pay attention to what he says. He has the opportunity to promote a more thoughtful and consistent approach to building software, but doesn’t seem interested in exploiting it.
CryptoCoinJS
Is sshfs a serious replacement for nfs? I've got a Buffalo Nas at home that I use Samba for, but Samba is too slow to watch hi-def videos over. NFS seems to be a pain in the neck to get working on that particular device, and I hate using it on a laptop. I guess I should probably just try it, but I can't see SSHFS as being any faster than Samba.
I'm assuming this is made with nanotechnology similar to Neverwet. I haven't looked properly into it but I remember reading that there is suspicion that nanotubes might be dangerous like asbestos. Imagine cars with this coating crashing, sending dust of that stuff into the air..
Tests are useful on many levels, but at their most basic they provide a second client for your implementation...

I like to say that the tests are the first client :)
IBM launches Cloud marketplace
10 C-Level Positions That Are Red Flags For Funding
I'm just waiting for them to test in snow.
It's been fun to watch the E-MAIL --> E-Mail --> E-mail --> e-mail --> email transition
Openstack in a Box – Setting Up Devstack Havana On Your Local Network
Can we just use this on our cars? https://www.youtube.com/watch?v=IPM8OR6W6WE
Your site came as inspiration to us on a project we're working on. I'd like to learn more about it. ryan at skycatchfire dotcom
Sounds like you need to fire the person who curates your Twitter feed.
I think danielweber is referring to systems designed to intercept and destroy ballistic missiles, not to ballistic missiles used for defensive purposes
It's important to note that the top answer is hand-tuned to work with that specific image. It probably doesn't generalize well.
That sounds very correct, and is true for all the dominant industries in New York: Finance, Fashion, Law & Media.

It leads to a lot of savage energy channeling through the system, a lot of deep career dissatisfaction and a feeling that someone, somewhere is tightening the rack, with you on it.

I suspect the only real winners in the city are the landlords.

Whatever the cause, in all my time on the road I have never come across such a congregation of pessimists as I did in New York.
Here is a t-shirt that is available to preorder and has similar features. It says the effects will hold for "up to 80 wash cycles".

http://silicshirts.com
Don't get your hopes up, that brainwashing is still alive and well with the first word of Google's post being "Jaywalking".
EBay’s Devin Wenig on Retail in a Post-Mobile Age
Finland has had this since 2012. It really helps small companies who develop gis and map applications as well as hobbyists.

http://www.maanmittauslaitos.fi/en/opendata

http://www.maanmittauslaitos.fi/en/opendata/list-of-the-digi...
Mine was a provocatory title. What I want to say is: opinions can be right for some people, wrong for other.
I don't think the idea in the post was to perform throttling in the client. The idea is to provide a best practice handling of throttling in the client (e.g. what to do when receiving a 429). Since the 429 is mentioned in the article, it's a reasonable assumption that the throttling happens outside of the client.
I'm with you on testing GUIs and (mostly) stored procedures. I would add low-level interfaces (hardware, OS, third-party library implementations) to that list.

Algorithms are certainly testable with TDD though. In fact, they're probably the easiest thing to test. Maybe I don't understand what you mean by algorithm, but things that can be expressed mathematically (sorting, searching, decision trees) are very straightforward to test. Tests can even be reused to verify multiple algorithmic approaches to the same problem.
Don't screw up your landing page. 9 mistakes easy to avoid
See also the pleasingly named Weasel Words.

http://en.wikipedia.org/wiki/Weasel_word
I don’t want to sound like a stuck record, but did he actually say that? My interpretation of his keynote was that he was “blindly pretending” that there are only negatives to test-first development, unit testing &c, which is just disingenuous as the scientism you’re highlighting.

I dunno, maybe my biases are preventing me from understanding him properly.
It'll probably be less performant than NFS, but is a really great and simple way for mounting remote volumes securely across the internet without having to worry about VPNs or any extra authentication or anything.
This article gives an overview:
http://www.adhdenvoeding.nl/cms/wp-content/uploads/2012/12/A...

In the first table, second column (RCTtype) everything starting with DB is a double blind trial. (5 in total)

Pears/Apples?
It has something to do with the hypo-allergenic qualities of pears, rice, turkey and most vegetables.
But I'm not a food scientist.
You'll have an uphill struggle if you want to stop TDD being mocked ;)
I had the same exact problem with a side project that spiraled out of control and was eventually cancelled in favor of a new job. What I had just started at the end, and what friends have done, that seems to work really well is to use something like Trello or Asana (which is a semi-ironic recommendation since my project would've been a competitor to these two) and lay out your immediate goal right now. Don't write any more code until you have that figured out. Then start entering tasks/ideas/features/bugs/etc that get you from wherever you currently are to that point.

I know someone who did this and has become disciplined about going back to that list whenever he starts working on the project to make sure the idea he's working on is on that list. If it isn't it's added to the "maybe one day" list on Trello and he switches gears over to some other task. Keeping in mind that tasks could be writing code but they could also be market validation as well. Of course he still has the issue of re-writing half of it every couple of weeks when he thinks the "old" code is now crap and needs to be refactored to perfection. That's a slightly more difficult hurdle to over come in my opinion.
IBM Cloud marketplace
Ask HN: How to increase web traffic?
best way to increase web traffic?
Twitter is big and I personally don't have that problem.
So I'd guess that this is more of an issue related to the people you follow instead of Twitter itself.

Unfortunately Twitter can't know which content you'll like so there is some work required to build up a feed that continuously delivers this content.

This seems to be one of the major issues when it comes to joining Twitter nowadays too.

PS: Title feels very "sensational"...
It's funny to see Uncle Bob take offense at being called a fundamentalist and then follow with this gem:

> If you aren't doing TDD, or something as effective as TDD, then you should feel bad.

"Fundamentalist" is hyperbole, which is par for the course in blog posts that want to attract traffic, but the sentiment is real, and Uncle Bob perfectly demonstrates that the qualification is justified. Like most extreme advocates, he's trying to get us to believe in something based on faith instead of facts.

"If you don't do it, you should feel bad".

Last time I heard that was in a church.
I hadn't realised they operated in London until this. However I'm now completely put off ever using them by the greedy opportunism here and recognise their name as some kind of creepy übermenschian far-right libertarian cultural import.
> I'm not sure I understand. I've written thousands of tests over the years in strongly typed languages, with third party dependencies.

Usually there is no way to mock that DB connection happening two layers down in the compiled code inside the .dll/.so/.a/.lib.

With a dynamic language you just monkey patch it, after some debugger introspection.

> Further, I've written complex algorithms and data structures with TDD (in fact that tends to be when it is most useful).

How did you design cache friendliness, memory layout optimizations, O() access times, with a "write test, fail, write code, success" approach?

> UIs are more complex to TDD that is true

Yes, and most important TDD fails at the UI design part, specially on native UIs.
Thanks for the feedback!

I could definitely pull the information right into the email.

My only concern with that is having the letter be too long. As it stands right now I include 20-30 postings per mailer.

I could break it up into multiple mailers as well. So something like 10 posts per mailer with a layout like such:

[Company]
[Job Title]
[1-2 Sentence Description]
[Location]
[Salary] (I could possibly pull in a salary from Glassdoor if this isn't provided)

Would that be more attractive?
Rewriting Avira's SPA from Backbone Marionette to Angular
surely you're joking by including WhatsApp in this list.

we can't all be privy to Mark Zuckerberg's paroxysms. let's not confuse the astronomically weird actions of child with too much money for anything resembling reasonable investment behavior.
What about this: fiddle around and just learn/goof until you stumble upon something that you will want to finish. There is not that much value in finishing something no one needs and there is no point in turning hobby pet time into work unless there is some gain (money, inherent motivation, proud feeling) from it.

There is value in learning and trying out things and chances are one of those things will motivate you to do something "real".

To be concrete, two things worked for me:
a.) Define deadline, either end of week or end of month. It does not matter much. Your goal is to get the whatever into some finished state - smallest think you can get away with calling done. Done, not perfect.

That will force you to keep scope small and do all that finishing work. Plus, if you pick up something you do not like, it does not matter, end is soon. Next moth up pick up something entirely different. Repeat until you either get bored by that or stumble upon motivating thing.

I found these inspiring: [1] and [2].

b.) Define smallest possible deliverable you can from current project. E.g. proof of concept prototype or tutorial/description blog post. Work on it until you have that smallest possible deliverable. If it was motivating continue, if it was not motivating pick up another type of project next time.

It is similar to a, but it does not have hard deadline. However, point is still to keep it small and try various things before going big.

[1] http://www.gamasutra.com/blogs/RamiIsmail/20140226/211807/Ga...

[2] http://gamasutra.com/blogs/ThomasPalef/20140225/211663/What_...
I see this as an interesting business lesson for startups, but even more general.

First, what a great marketing angle, a self-cleaning car, how cool is that! I imagine 6 o'clock news stations across the country showing clips from this video tonight.

Second, what a great up-sell opportunity. Now every oil change service done by Nissan can include a new $50 charge (or whatever the market will bear) for re-applying the self-cleaning paint.

Third, could they even push an environmental angle? Ie. litres/gallons of water saved by not going through a car wash?

So, with one new feature Nissan has gained free marketing, and an incremental revenue source for their dealers. Not bad for a mature market.
I agree with you, just a note, "practical pragmatism" is a pleonasm http://en.wikipedia.org/wiki/Pleonasm