feralmoan

Brilliant work guys

user sessions would get picked up by if you just injected the oembed player dom rather than hand-rolling it (https://developers.soundcloud.com/docs/oembed) - no authentication required.

why this over a cat | sed | sendmail < bcc distro_list?

yerp, fixed width nacha files exchanged periodically over sftp. Built for/by cobol based banking systems back in the day and continues to live on.

very slick

"Unfortunately, we’re still in a world where a manufacturer’s first reaction is to lock things down, to make devices incompatible, in an attempt to extract as much profit as possible from the system. If this is your mindset, you’re not going to release an API (as Philips did), let alone encourage your competition to build on the same API (as Philips hasn’t)."

Yeah, IoT protocols are a warzone, hell, few companies/coders are even able to agree on general web API architectures (REST/RPC/SOAP - and everything in between. puke). Add MQTT, CoAP, XMPP or whatever other pet vendor protocol or semantic layer into the mix... total nightmare. What's left are a bunch of consumers hung out to dry because a these big old guard companies haven't learnt how to collaborate and deliver broad spectrum value to their customers.

A lot of hand-rolled integrations for many years to come! Whoever can alleviate that pain will likely end up dominating

For me it helps taking short breaks from one problem (like, ~20 mins every couple of hours) to lay the foundations for tackling the next problem, drawing diagrams, doing some research and letting a project 'normalize' conceptually. Small context shifts kind of count as 'breaks' (to me, anyway) Its much easier to get into the zone when everything already fits into place and you have a clear purpose, than having to battle with minutae frustrations and rollbacks of badly planned work sprints. I think if you just rush into a problem it creates a kind of impedence mismatch between your expectations of productivity and what's realistically possible and kills the mojo. So be Zen. Take ya time and do it well :D

... and if you get your meetings and lunch done and behind you by 1130am that's like 6 hours of a straight working afternoon with no planned interruptions :D

Storm doesn't naturally support dynamic topologies and is rather resource hungry, which needs a bit advanced planning. I was looking @ Storm for my own pipelining product (bip.io) very early on and shied away as too high an opportunity cost for self-hosting users/devs to be bothered with. On a Rasberry Pi for example, forget about it. Without being able to create dynamic graphs it otherwise just ends up being a simple message bus (anti-pattern).

why do people insist on making candidates write code on whiteboards anyway, its the exact opposite of 'right tool for the job'

JWT is an interesting standard (http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-1...) dealing with sessionless temporal auth tokens that offers some flexibility between http basic (native) or signed tokens using the same credentials. If you're not using TLS you're kind of screwed anyway, whatever the auth scheme!

This is a treasure trove, thankyou!

This is great! Can anyone suggest a place where coders can reach out to people in non-tech industries and solve real problems for a change?

http://www.highcharts.com is amazing and used across a lot of the US's biggest investment banks. Creative commons version available or per user/organizational licenses.

http://d3js.org though I have a particular soft spot for.

Really enjoying all the new tech startups that seem to be emerging from Barcelona. Nice work :)

How long are people usually spending to write a blog post? Is 1-2hrs reasonable, because i get an hour in creating some story that people probably won't read and just go 'to hell with it'. Whats an average time investment, for those who are out there doing it?

And node-phantom-simple :D (saved my bacon with that also)

Same here, between Nodemailer and Haraka, SMTP relaying with node is a breeze

Don't E visas have prevailing wage constraints which you won't come anywhere close to meeting in an incubator?

A lot of love here for wit.ai, I was thinking about transactional contexts today (NLP conversations) and if I could support that kind of workflow with wit and 'oh hey there ya go its already in there as states!'. Great work!

I've used a bunch of different languages over my career from device+graphics libraries in assembly to windows apps to servers, web stacks and (recently) front-end. These days admittedly I do a lot of node development and while not a huge fan, its really so easy to get something up and running all the while using all the same tools and even the same modules on the front+back ends. When I run a build its the same gruntfile for the stack and UI, there's no fussing about getting disparate servers, paradigms and teams playing nicely and its small enough for me to get an entire application installed and running literally within a few minutes even on resource limited hardware like a rasberry pi - that creative freedom is brilliant! I can definitely rant about all the things that are bad about nodejs but as a prototyping tool or sideproject toy its really valuable.

AOP type architectures work fairly naturally with out of band queues etc. (0MQ, RabbitMQ or Redis pub/sub off top of my head) so its never really difficult to parallelize those requests out to workers who can largely operate independently. HTTP isn't a silver bullet and for the most part its how public API's are defined - however within your own infrastructure there's a bunch of other transport options, protobuffers, thrift, msgpack or whatever. But yes building some kind of hypervisor or FSM to manage error conditions across a cluster and particularly across datacenters can get out of hand very quickly

Really wish there were better defense attorneys onboard in these cases because at their core these instances boggle the logical mind.

Definitely a lot of overhead keeping sockets alive for this when deltas must be few+far between. Wonder why they eschewed mqtt or rest... ? I imagine a lot of integrators are going WTF to a Firebase approach for a thermostat.

I'm going to say FU to the industry and buy a horse ranch if it is! These were all public documented endpoints and 'worked as intended'. criticker is next-level incompetence, that's pretty much the point.

BipIO - https://github.com/bipio-server/bipio is all JavaScript, the biggest thing it needs right now is a migration of the configuration dashboard at https://bip.io into the public repo.

Currently a Backbone/LESS/PHP(Zend) stack and needs some CSS consolidation, a decouple from PHP, (most of this is already done), a Gruntjs build system, security audit and general cleanup and also an Apps/plugin framework

oh and there's also Templar (http://mjpearson.github.io/templar/) which could be a whole lot more awesome :D

I think OP was writing a parody piece and not actually serious.

I think we'll see a lot more automation on the product development side before it starts to cut into software jobs themselves. With so many automation frameworks popping up and big movements towards open API's and IPaaS systems which make a huge range of "cloud" components available out of the box, attacking the taxonomies of product abstraction and sticking an AI layer ontop of it seems fairly plausible if not natural. I'd love to see a time in the industry where you just go 'hey computer build me an MVP which does X-Y-Z I want to test some crazy market' or 'hey augment this existing product with some new interaction' and then figure out if a product is worthy to live. Until machines have real sophistication, we're going to need humans to keep adding their creative 'secret sauce', anyhow, and software people to code along the edges until whatever else can take over.

There was a lot of good advice in the article, I think its a big creative leap to say someone who travels, understands their needs, dresses how they're comforable, finds inspiring friends or has a strategy for personal growth is somehow a 'cruel jerk'. On the flipside I've met people who are insufferably subservient to the status quo and they are literally the most boring and uninspiring people on earth.

grid virtualization for the web has been around for a long while with things like slickgrid/extjs (google docs is a great example), maybe there's a good open source project opportunity in writing a virtualized+paginated+history friendly infinite scroll

Worth it for the hint on MkDocs alone - thanks Eric Holscher!