HN user

thedaniel

473 karma

maker of things with computers

Posts10
Comments74
View on HN

They aren't, exactly. In one of the articles linked from this one, it says

It’s easy to confuse the ePrivacy regulation with the General Data Protection Regulation, a broader law addressing consumer data privacy that has dominated the market’s attention lately. The core difference is that cookie use is central to the ePrivacy regulation, which is why it’s known as the “cookie law.” Businesses in Europe must get explicit consent to use cookies and provide clear opt-outs to users under the proposed new law. Meanwhile, the GDPR regulates the general handling of personal data.

Best Slacktices 9 years ago

Disagree. Private messages are the analog of walking over to someone and just talking to them, and one-on-one discussion has valid purposes (e.g. discussing user stories or parts of the design before writing a spec)

Perhaps you disagree, or perhaps this is when your organization absolutely has to? ;) One-on-one discussion has valid purposes, even if the purpose is to reduce noise, but it's important not to err on the side of private messages because institutional knowledge just disappears, or never gets cemented in the first pace

Best Slacktices 9 years ago

I very nearly added an extra point "manage your notifications" with a simpler subset of what you posted here but decided it didn't fit in the in the tone and spirit of my post

In the water distribution section the author mentions the other gardening software doesn't mention how they distribute water. There's a longer history of irrigation than there is of embedded software development, so maybe he should have talked to someone that actually does agriculture or googled 'irrigation system parts' and bought one of the thousands of existing drippers for a buck.

Of course the later heading "the gardening wasn't supposed to be hard" seems to imply that he assumes non-coding skills are easy to figure out or obvious, which is a sadly too-common trend in the tech world.

cosign for splice, i have been using it since beta and now it's an essential part of my workflow - i don't really use their collab stuff much (just to send people projects, not to actually collab on them), 90% of my use is backup and versioning. Still I can't imagine going without it.

* Only a single project can be open at once, which makes copying from old projects tedious unless you shuffle files around into your current project.

You can drop entire projects from the Finder into open projects, which is clunky but does make things a TINY bit less tedious

The parent mentioned probably the two biggest mail clients in the world, and you mentioned 2 that I haven't heard of despite 20 years of sending email and toying around with new software.. I'm not sure it's an effective rebuttal.

This is a paraphrase of a semi-well-known quote from a respected business professor named Warren Bennis, about the "factory of the future" - who knows whether he coined it or adapted it from a common joke though. Here's his version of the quote, which I like a bit more:

The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment.

This was an honest mistake on their part

From my outside perspective, it doesn't seem like a mistake on their part at all. Later in the thread you say this accounted for 10% of traffic, mostly 404s. This is (i assume) a hell of a lot of requests, but given npm's position as developer infrastructure, I don't think they could have reasonably expected to melt it. It would have been good of them to give a heads up, but I don't think I'd start assigning blame to the Code team.

GitHub Audio 10 years ago

Splice.com is this, and it's great, I use it with Ableton all the time. Versioning is easy, merging is impossible. But it's better than what I did before.

Along those lines, it would be wonderful if someone would write a coffeescript implementation that output clean, idiomatic ES6 rather than ES5!

Atom 1.0 11 years ago

We've been working on Atom for a long time. I think that CS was a great choice when it was made some years ago, and I can say that the core team quite likes ES6 (which directly addresses a lot of the same JS warts that CS was designed to avoid). That said even if we decided to move to ES6 today, it's a big ship and it takes a long time to turn :)