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 simply can't commit the time to roll something in to a product or platform which I may have to roll back out again later when there are alternatives that I can plan/budget/account for. There are a few things lately which I've thought "that could be great" but I haven't adopted or tested fully because I just can't know how their costs will scale as my products do. See Bridge for another example, though they did respond with extra clarity after a few people mentioned it.
Your "constant drive to simplify" is better understood as a constant drive to improve. Local maxima are dangerously beguiling, we should always question.
It's pretty disgraceful. Thankfully it is beginning to be flagged up as more of a problem as some of the better newspapers are beginning to do some proper investigative reporting.
I'll be keeping an eye on it anyway - you never know when something like that might solve a problem you encounter.
Discovery and dynamic usage doesn't seem to be covered in many of these projects (cool as they are) which seems to me to be a more challenging and useful extension.
It's also not really an HR thing, IMO. It's almost a "bypass HR" thing - it's so much better to have the devs/designers/whatever coming in to work and saying "there's this great person we should hire". Impress the people you'd be working with - not the ones who work tangentially near them!
Makes me wish I was in the position to offer roles - just the act of getting off their arse and doing something like this is a great start from anyone.
From this I'm assuming that the company they used for this (Bango I believe) would have been sent my mobile number in the past if I ever tried to access content they thought should have been verified. There has not previously been any messaging from o2 around this. Disquieting indeed. I would not have agreed to that transfer of information (nothing to hide, but it's MY information).
This is an appalling privacy hole, one which O2 have not publicised at all and from the contents of the tweet discussing, seem to see no issue with.
EDIT: a direct link to a checker by Lewis Peckover which shows this in action if you're on O2 - more verification wouldn't hurt of course. http://lew.io/headers.php
I don't know if you're saying it's a bad thing that airlines can no longer fire the recently un-hot, I'll give the benefit of the doubt and assume no. Do you think that the service being better on the airlines you mention has any real link with hotness, or just incidental correlation?
Heed this advice - just be aware!
Here school IT is generally centrally managed by an IT team who are not generally receptive to ad-hoc software installs. SaaS models fail due to firewalls and network access restrictions. Preferred/accepted bidder lists are rife. Teachers have NO budget for software.
I looked at selling to teachers here and decided that it was more hassle than it was worth - the market barriers to entry and borderline corruption/incompetence just made it a non-starter.
Wow. Do you find that many people keep listening to you after this or is this just a strategy to free your time of annoying "people"? The *nix community is generally quite friendly, but it doesn't grow faster because of statements like this. Sure, maybe it's a valid opinion but hell, at least explain why they should care!
But actually I don't think there's much wrong with this. It is OO. It's not domain object oriented, it's just OO. you're creating an object which has a single responsibility - to calculate a sort order, or to take something and present it.
While GoF disciples may well have made many mistakes, this doesn't mean that this kind of OO design which emphasizes separation of concerns is wrong. It may look more complex, and perhaps it's a premature refactoring - we don't know out of context. But these classes are doing more than "just wrapping" something. They're promoting the concept of "displaying" or "sorting" or "calculating a rate for something" to a first class concept in your system, and in the process making it easier to change the implementation and to test in isolation. They're not from the problem domain. But they make sense in your program domain. And that's fine (if not abused).
Edit: (as sibling reminded me of a point to make). Some of these classes could be functions if your language supports that. But they don't have to be, if making them classes makes them easier to work with, test and understand.
And surely bringing up something like Haskell is germane? The article implies that this is the best/only/right way of dealing with issues like this, when that definitely isn't true for languages with a different/stronger type system, as one case.
Of course, this is pure opinion and supposition on my part - I suspect a proof either way is NP-BloodyImpossible. I do feel like coding conventions such as those he suggests make code harder to read, even if only a little bit. And that's ignoring IDE support as well - I feel the same if I'm in Emacs. If there are enough things in scope that I can't hold in my head the relevant [meta] information about them for that usage, that's a problem for me, probably of quite a different kind.
Now you have something which can still look clean (how clean may depend on your language, type inference, etc.) without bringing in messy pseudo-Hungarian-ness, which stops me doing the most important thing with my code - reading it easily.
Obviously it's only a silly and trivial example, but I'm not sure this article has dated that well in some regards (or perhaps only really applies to certain types of languages - Visual Basic, for example, pretty much forces you to do something like Hungarian to maintain any semblance of sanity long term).
I'm not sure I'd agree with the last point about time - I think that balancing business generation, expansion and refinement is possible - but perhaps not so much amongst startup size businesses, which is more HN territory. In that case it should certainly be looked at as "is it better to try and get 0.1% more people to click buy or 20% more people to arrive" - or whatever you think your likely ratios are, hence cost/benefit call.
Don't get me wrong, I find those design elements you're talking about to be far from my tastes, but provably I'm not "normal" within the markets under test. At what point what you say to a business "you might make more money like this, but don't do it anyway because it's awful"?
Apologies if I'm reading more in to your statement than was intended. I've seen enough of your work to know that you get both design and business hence I think that statement interesting!