1,625 karma · joined December 25, 2008
Tech Theory + Practice. I care most about changing the world in meaningful ways through technology. I care very little about yet another X.
Contact me at andrew at xyncro dot com.
irc:kolektiv:irc
[ my public key: https://keybase.io/kolektiv; my proof: https://keybase.io/kolektiv/sigs/0d5gliRyPmqTUqjf5C4XNh5y1sry6und7d3z4LYWCyo ]
I can imagine that this sentiment is probably against the prevailing HN mood, but I've been thinking a lot lately about how certain kinds of thought and investigation are only enabled and supported by certain structures. The point of a university used to be being the highest pinnacle of thought. A place where people could have everything not related to intellectual pursuit taken care of so they could devote themselves to the pursuit of greater knowledge. Now that seems to be replaced by a corporate campus.
It's a cliche, of course, but how many breakthroughs of meaning are we missing out on because the brightest and best of our generation are now no longer seeking after truth, but instead seeking after a way to make more people click on an ad? Ah well, it's late, and as ever I'm post-sober. Best of luck to him and his team - I've enjoyed his lectures and papers. I hope they may continue, but I sadly suspect not.
If you needed to do this, you'd use something that already exists - if you just wanted to do it in Node, for some particular reason, why not just use plain requests and an HTTP parser?
I don't mean this to be overly critical, but just in case anyone's thinking this would be a good idea - there are better ones. Just to learn from, fair enough.
As the article says, if your people aren't bothered or motivated by your goals, they probably shouldn't be there (at least in skilled positions - of course there are plenty of jobs which are purely for the paycheck). It's not worth changing your company based on the attitudes and motivations of people who shouldn't be there anyway.
It is easier to hide in (many) big companies, but that doesn't mean that the solution should be to remove all potential hiding places - it should be to remove (or re-motivate) those who are hiding.
If they want to, sure, but nobody has a right to expect that from others, in the same way as founders have no right to expect the same level of dedication from employees without the same potential for reward.
[edited for minor punctuation]
Does it? Because from all the information provided publicly it seems to apply to all remote workers - are you sure they're all lazy moonlighters? Doesn't seem probable.
And don't apply your own experience to everyone else where it doesn't apply - I work from home a lot too - I have no dogs, no kids, no smells - in fact I have a very nice office, with better equipment and environment than any client I've ever worked with. But that's just me, of course.
It is perfectly possible to joke about horrific things without intending to condone or support those things. That said, the place for these jokes is unlikely to be in groups of people you don't know at tech conferences. That's insensitive, rude and often intimidating - so don't.
When presented with just a problem, and no hint of where to find a solution, the end result has often been a mix of horror/terror/anger/paralysis. They have all of the knowledge required in the toolbox, but no practice at applying it in non-directed ways or of having to try (many) failing ideas before one works.
Very good luck with your teaching - I wish we had a lot of teachers over here who thought the same way.
I am assuming mediate should be meditate, unless you really want my help in a peace process (not wise).
What you should be learning from the things that "your geeks" (blech) dislike, is what the rest of your company also dislikes but isn't telling you. The fact that you can fill in the timesheets for 15 people should show you exactly how pointless they are. You already know what they're doing! What are you trying to track exactly? I'm presuming you're not paying them based on the timesheets, otherwise they probably wouldn't let you fill them in.
That's just a small example. You don't have some weird sub-species. You have people who are attuned to certain things as a side effect of their job/life choices. Now work out what the rest of your company are attuned to, and go and listen to them as well.
I don't really think I'm being elitist - but I will admit that I'm talking about a sector within a market. Clearly I'm not talking about fast food, I'm talking about a specific type of dining experience. If this technology existed within a KFC (and was executed well) I'd like it (yes, I'm that weird guy that likes good dining and the occasional meal of absolute junk...)
I don't think that most restaurants currently piss off customers though - if they did, they'd generally be broke I think. I think you're assuming that the changes you suggest would make the best even better - and I genuinely don't think that would be the case. I think that character, personality, idiosyncrasy etc. are the makers of a great restaurant as much as the food, and I didn't feel like these ideas fitted that - at least within certain markets.
If you're ever in London and you fancy a discussion about what would really make for an incredible restaurant, and you fancy discussing it over wonderful food, give me a shout...
(Dinner's on me, of course)
It's not about efficiency, it's about atmosphere. I don't want a glowing screen anywhere near my dining table. I don't want anything which helps me order "what I had last time". I don't want them to ask me about the last time I was here 3 years ago either.
Can we invent and work on technology which adds to the beauty and experience of life next please? Either that or get the brain in a jar thing working.
I would call it a hatchet job if I could tell by reading it what the target is, but it isn't even good enough for that.
The rest of the article is just random presumptions thrown together, for what reason I couldn't say. The best developers work in finance because the money's highest? Yeah, OK then... (To be fair, I think there is a qualifying "considered to be" in there somewhere) K is impenetrable? Hmmm. Haskell is an offshoot of ML and unreadable? Umm, factually wrong.
There's lots wrong with software at scale, and the pressures of financial institutions along with high budgets etc do produce an interesting set of problems, but this article offers nothing new about anything at all in the field.
As an aside, I already don't trust an author when they start off with a claim that textbook code is good code! It's almost universally accepted to be trivialised and simplified to the point of "don't do this in the real world" simply because it has to be. Some of the worst code I've seen has been in textbooks (and that's worst as in "dangerous" rather than as in "badly written and in need of refactoring/replacement/enclosing in concrete).
Edit to note: I think it's actually beyond incompetent journalism and in to plain lying to present a piece of code as evidence of Haskell unreadability when the link to that code on SO refers to it clearly as "obfuscated Haskell code".
Of course, that's rather a digression - it's a surprisingly decent standard, and what it's enabled is startling. Well deserved, and congratulations to them!
You're right in saying that, for example, exactly once delivery is a symptom of a business requirement. I do agree, but even something like message de-duplication has issues with scaling in a genuinely distributed system. Admittedly, whether you choose to look at that as part of messaging (a term which I admit to possibly over-broadening sometimes, as I tend to look on it as more of an approach than a technology) is open to debate, but I do get where you're coming from much better now.
On the second point, I wouldn't describe my scenario as a distributed transaction - there's also very possibly no single server on which to do a classic database transaction - as soon as you do there's a scalability barrier. Anyway - it's more a difference of scenarios I think, and I'd agree that in the ones you've described the solutions sit outside of a messaging layer/domain.
Always interesting to hear, thanks for clarifying!
Guaranteed delivery is indeed easy if your messages are idempotent, but if they're not then life is significantly more difficult. Most messaging systems have an "at least once" guarantee, but building in an "exactly once" guarantee, especially with a system with any significant distribution doesn't seem easy at all (tell me if I've missed something though, but event ordering in distributed systems has a reasonably interesting history).
The same obviously applies to message ordering. These (presumably incrementing/timestamped?) ordering identifiers are fine if they don't have to cross a sender/batch boundary, but plenty of situations are more complex than that. How do you "simply" avoid the problem of either centralised synchronisation or time slip in ordering, as well as out of order delivery with major partition events?
Just curious as to whether you're saying that these are all easy problems, or that the domain is easy if you have enough constraints!
I also have to admit that trying to in effect argue that people should not be prevented from "driving stoned" (yes, I know that's not really what they're saying - I hope!) is a peculiar strategy to get the majority of people onside. I rather like a drink. But I wouldn't argue in favour of drink driving.
Just had to pick up on this, purely because it's symptomatic of another form of blindness. We DO have Asian people. Go and look in Asia. There aren't many Asian programmers in companies in my current town because the demographic is not a small scale mirror of the world demographic. I wouldn't expect to find even 8% white guys in a programming office in Manila.
That's not to ignore the fact that certain sections of populations are, for whatever reason, dramatically underrepresented in companies in various prominent countries, but throwing around random meaningless soundbites like that doesn't help anyone's argument.
Moving on to an entirely disingenuous non-apology ("i'm sorry you were offended" vs. "i'm sorry I offended you"), it doesn't get much better. Then on to an appeal to authority - we tried it with other developers and they didn't care at all.
The thing is, I can't criticise from a business level. I have no idea what their internal world looks like (we can all have our own guesses). But the message is inept at best. The upshot is that it's hard to imagine anyone building something (innovative or not) on the Twitter platform. If it's within the TOCs today, would this message give you confidence that it will be next week?
By attempting to kick out half of your hangers on, you end up kicking out all of your hangers on. Seems like a lesson worth heeding for giants and hangers on alike.
Most people a) don't have a reader b) don't really know what they are. Compare this to something like a URL/domain which people do recognise the format of, or a discount code ("use SUBWAY10 for 10% off!") to achieve the same goals.
Seriously, I would love to hear of any use cases where a QR Code was the absolute best approach.