HNHacker News
TopNewBestAskShowJobs

neilellis

911 karma · joined February 1, 2012

submissionscomments
neilellis··on Facebook Relay: An Evil And/Or Incompetent Attack on REST
I think for application status codes it makes sense to always return 200 and do as you have done.

Of course, if your API has received bad data then better to return a 400 and a similar payload.

And if your application has caught an exception which is not part of any form of validation then better to return 500 and the payload.

Got to do the best we can with the hand we're dealt hey!

neilellis··on Facebook Relay: An Evil And/Or Incompetent Attack on REST
HTTP error codes are something of an embarrassment to the web.

We have more codes for April Fools jokes than some of our most common situations we deal with. We have some bizarrely specific codes like Payment Required and Requested Range Not Satisfiable yet almost all real world application responses get dumped into 400, 500 and a few other codes.

How about more specific and useful codes like:

Parameter not Supplied, Parameter Name Invalid, Parameter Value Invalid, Url Path Invalid Format, Could Not Parse Data etc. etc.

This would also allow client libraries to decide better on how to process errors (i.e. as application or systemic errors).

I'm sure folk have better suggestions than I but I can't imagine many folk genuinely feel these existing codes are expressive for the modern (API centric) web.

neilellis··on Facebook Relay: An Evil And/Or Incompetent Attack on REST
LOL, yes that is a very good point. And how does the web solve this, by reference :-) Which is of course how you always solve cyclical graph representations in my (for sure limited) experience.
neilellis··on Facebook Relay: An Evil And/Or Incompetent Attack on REST
I think there were some basic pointers in there, but yes I too would have liked some examples on how to do things better.

As much as I dislike people critiquing from a purist point, I also dislike my own ignorance on things that could keep my life simpler.

neilellis··on Facebook Relay: An Evil And/Or Incompetent Attack on REST
A large group of smart people often produce some really dumb ideas, like 'Google Wave' - so I wouldn't personally use 'Proof by Large Group of Smart People' in this case. Hacker News has been the home of many a bad idea by smart folk.

Instead, maybe we should all be critiquing the points raised.

In my limited experience, most engineers (yes including very smart ones) are more enamoured with their own ideas (and not discounting myself here!) than learning other people's work well. And the critique I read didn't seem unfair in that respect, more so it encouraged me to look deeper at HTTP first before I add something into my apps own protocols. Which to me is a good thing.

Especially around content negotiation which I had not looked at beyond a superficial understanding.

For the record I ain't no purist :-)

neilellis··on Facebook Relay: An Evil And/Or Incompetent Attack on REST
I have to agree with this article. There is a tendency in tech to reinvent what we don't understand properly, and from experience of using third-party APIs (and from my own ignorance too) - HTTP is the thing we seem to know the least about (well actually one could argue TCP/IP is ...)

I read this article from top to bottom and I didn't feel the comments were extreme or purist. It did leave me thinking we need to spend more time learning and sharing knowledge of HTTP /REST than dismissing it.

Of course, the headline is clickbait - and that is the only real criticism I had.

neilellis··on XStream: A Java 8 Stream extension to process data pipelines the uniX way
Unfortunately the name clashes with the general Stream library from ThoughtWorks (http://x-stream.github.io)

That said, it looks like a really excellent idea - the stream library in Java8 is powerful but far too complex for simple jobs.

neilellis··on Lovefield – A relational database for web apps
It's like having PouchDB -> CouchDB but with SQL not NoSQL

For me I'd like to:

Firebase as backend. Sync user data to browser. Query user data elegantly in browser using select statements.

neilellis··on Echochamber.js
Do I need to point our the irony?
neilellis··on Echochamber.js
If you think you're a victim of shadow banning on Hacker News can you leave a comment here ;-)

Hey downvoters, get a sense of humour - sheesh.

neilellis··on Echochamber.js
Can you make a version that works like Disqus but filters out anyone who disagrees with my opinions.

I'm guessing someone's already implemented this on HN judging by the downvotes ;-)

neilellis··on How Big is Space?
It was in Flash and I was too scared to click :-)
neilellis··on How Big is Space?
"Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist, but that's just peanuts to space."

Wanted to be the first :-)

neilellis··on Ask HN: How do you get good domain names?
1) Get your domain name before you name your product :-) a lot cheaper that way

2) Don't break my two tweaks rule. Which is, take your ideal name, now make one change to it so you can get the domain you want. I.e. change letters, mispell it, spread over the '.' etc. But don't make TWO changes, TWO changes looks naff. One is acceptable. (Obviously this is a rule of thumb).

I'd also add, be creative, there are lot's of ways to create cool domain names (as you can see from YC companies), but as @fsk said, CHECK GOOGLE! once you're done.

Especially try not to have a valid dictionary word as a product name unless you are Apple - the reason for this is you'll want to have Google Alerts and track mentions across blogs and social media. You can't do this if you've chosen a commonly used phrase or name.

Interestingly this is why Marina and the Diamonds named her album Froot ;-) true story.

neilellis··on We Tried Slack and Regretted It
I'm very disappointed with the level of comments here - the emotional attachment to Slack is just not neccessary; same for the ad hominem comments. For sure they have a great tool that I love and use but they have been slow to act upon the fact that many communities are using their free option with huge numbers. Rightly or wrongly.

Slack just simply need to decide whether they are supporting this model or are happy to hand it over to Gitter to deal with. I suspect Gitter will be more than happy.

Personally I think they could offer a fixed fee for public rooms. But hey that's up to them, it's their business model to decide.

I think the problem is just the lack of clarity about how they are going to manage what they definitely know is going on (I have asked).

neilellis··on Ask HN: What do you do if someone is already building what you wanted to build?
What she/he said.
neilellis··on Ask HN: What do you do if someone is already building what you wanted to build?
As the T-Shirt says: http://www.headlineshirts.net/its-all-in-the-execution-t-shi...

It's all about the execution. If two people have a great idea the winner will be the one who executed better.

i.e. They scaled better, they used appropriate tools, they had a functioning team, they moved first, they listened to customers, they pivoted and stayed agile, they remained focussed on their goal etc. etc.

On the other hand, some products have network effect, which can make them hard to assail once they've got momentum.

Also don't forget the 10x 'rule' - you need to be 10x better than an existing product if you're doing the same as an established product.

As others have mentioned you may also be attacking different market segments e.g. business/consumer, geographical region, age group, etc.

Come to think of it, aren't there one or two books on the subject ;-)

neilellis··on BlueGreenDeployment (2010)
Yes, I really like that strategy, not done it myself as a little (not a lot!) complicated for a small company.
neilellis··on BlueGreenDeployment (2010)
Yep agree, also keep the database schema a little soft - i.e. tolerant of minor changes.

( an example for SQL databases of this is having an 'additional info' field/table which has no value for indexing but contains additional captured info.)

neilellis··on BlueGreenDeployment (2010)
Personally I keep the database out of the equation, ala 12 Factor.

The database when treated as a unique exception allows you to just get on with developing robust infrastructure.

However for this to work you need to keep code off the database and treat database changes as migrations not blue/green deploys.

I can't say this enough, treat the database as an exception, keep it clean without code on it and with 'soft' schemas (ones that tolerate minor changes well) - then you can do b/g deploys easily.

Also let someone else host the DB where possible (or the same cloud infrastructure of course), it's just not worth the pain.

neilellis··on Nobody's Going to Steal Your Idea
You're right it isn't. But also he's right, that the odds are against all startups - so a competitor also has the odds against them too. In an unproven market this is so much more true!

In regards to comments about IP :- compression and encryption are two obvious IP led areas. But also those working in the cutting 'technical' edge - such as high speed trading may well have solid IP.

The thing is a lot of SV based startups (a lot, not all!) are driven to solve customer/logistic problems not technical problems so they are less likely to have IP - unless (grrrr...) you count business practises as IP.

However startups out of a University incubator are more likely to be solving technical challenges and therefore have richer IP. As seen by the comments :-)

The light is shone so strongly on public facing SV startups it's easy for us to forget how many different types of startups there are and how they execute differently. For example most customer facing startups don't need stealth mode, they need MVP. Not true if your product is IP lead, in which case you need to be stealth while you secure IP rights and test the product internally.

There's a lot of massively useful advice coming out of SV - proven by startup after startup - but there is also a tendency to view all startups the same. The very fact that they are different means you need to have smart folk at the helm to navigate their own unique course based on the experiences of others.

neilellis··on Nobody's Going to Steal Your Idea
If your startup is based on execution and/or customer relationship sure this is true. However some startups are IP based in which case this is not true, now admittedly there is a low % of IP based startups on HN.

Some startups can execute better than you and can be better funded. Remember Hojoki anyone, nope - Slack moved fast got the momentum, scaled and wham! Hojoki used to be better than Slack btw. However if you operate in the public arena most people will know or guess your plan as soon as you spin up your MVP anyway :)

Right now down to the elephant in the room. Apple regularly release products/features that look remarkably like 3rd party apps, but not enough to be sued. So yep, idea stolen, implemented and market cornered by a virtual monopoly.

The truth is a complicated thing and the word Nobody is just factually inaccurate.

I'd go with:

'You're more like to fail executing than have your idea stolen.'

:)

neilellis··on Hyper – Hypervisor-agnostic Docker engine
Speed and resources https://hyper.sh/why-hyper.html
neilellis··on Hyper – Hypervisor-agnostic Docker engine
Would be nice to have this on Macs too no more crappy VirtualBox ;-)
neilellis··on Ask HN: How to make the WWW a more permanent place?
The best answer to this I've come across is the idea of a P2P web (ala Bittorrent). If the assets are hashed then every version of a website (potentially) would be out there for you to retrieve. Then Archive.org would actually just be another P2P node to help guarantee content from becoming peerless.

I honestly wish sometimes we could re-architect the web to use P2P instead of point-to-point communication. It would be a lot harder to censor for a start.

neilellis··on Peeple Is a Smart Peephole to Upgrade Your Door with Caller ID
Now that is a good example of internet of things, especially for the vulnerable (ain't we all?). I like the idea that a record is kept of who visited.
neilellis··on Ask HN: What's better for long-run productivity: caffeine or no caffeine?
This may illuminate the discussion somewhat:

http://www.trinity.edu/jdunn/spiderdrugs.htm

Productivity is not the amount of work you produce it is how fast and well you achieve your goals. Worth remembering that too.

neilellis··on Show HN: cta.js – Animate your 'action-to-effect' paths
Great, yep that's what we need. I prefer to use animation only to guide the user - not for 'oooh-ahhh' Flash-esque nonsense. So a library geared towards just that would save so much time.

Well done - and thank you, looking forward to cross browser version!

neilellis··on Jvm.go: A JVM written in Go
Yo bitches, I am not an engineer - you may have noticed that this is Hacker News - not Engineering Weekly. I ain't never built any machinery - or designed no bridges - I'm just mo programming wit deez wild fingers.

Take it easy - until you know the language well enough to know when someone is using a complement like 'crazy sh*t' - I wouldn't rush to judge them. Context is everything - as the first two words of this comment attest. Context is everything :-)

neilellis··on Jvm.go: A JVM written in Go
I mean we carry stuff around from the days when we (the Java community) felt 'more is good' - you know the days of spit Java Blueprints.

> And there is no difference in the way Oracle or Sun has managed the JVM

Yet coincidentally more positive changes have happened to the language in the last 3 years than the previous 10? I see a language that was dying on it's feet coming back to life - so hence my feelings about Oracle's stewardship (right or wrong!).

> And finally again no idea what you mean by countess Java developers wanting to reuse their knowledge but in a different environment.

Almost every Java programmer I know and/or meet has their 'other language'. That they use to solve problems that Java has failed in. But a common frustration is the need to relearn a similar but subtly different syntax. Concrete examples are NodeJS (and hence Nashorn, Vert.x et al) for lightweight format neutral APIs. Android for mobile :-) so hat's a win. Go for systems (Python in the past). Objective-C et al Desktop.

For me there is no concrete reason why we can't have these in Java (language). But in doing so we need to be willing to throw away components that don't fit. I.e. existing APIs, existing philosophies. Java is much more than the language, however so when tackling problems that aren't large scale serverside applications we need to adapt if we are to reuse. This is an area that I very much am interested in seeing develop. My specific case in hand is Android - which reuses Java skills but has a lot less to do with normal Java programming.

Hope that clarifies a bit.

← PreviousPage 6 of 9Next →