adrianhoward

157 ms·

1381.
by adrianhoward 15y ago
True. It's easier to fix people sucking if said suckage is easily observable though...
1382.
by adrianhoward 15y ago
One reason is that it's not just your location that's the issue. It's your location + all the other public information I can potentially find out about you combined with your location. The combination of a lot of separate facts can, togethe
1383.
by adrianhoward 15y ago
I've taken a bunch of IQ tests over the years with some wildly different scores. I score pretty well. I'm also very sceptical of their general utility. The between the lowest and highest score I ever received on an IQ test is 45 points.
1384.
by adrianhoward 15y ago
And yet I've worked several places with some decidedly non-trivial code where we quite happily did do this. None of us were wasting half a day getting up to speed because of things like: * More of us being familiar with more of the code - s
1385.
by adrianhoward 15y ago
The article doesn't really resonate with my experiences of working with good Scrum teams. It does, however, sound very much like some organisations I've been involved with who have adopted one or two of the Scrum practices, but haven't real
1386.
by adrianhoward 15y ago
"I am beginning to think that even small teams should be split in two groups: feature and maintenance" Noooooooooooooooooo! :-) Seriously though - I'd go as far as saying that it's an organisational anti-pattern. Every time I've seen folk
1387.
by adrianhoward 15y ago
All too true. I'm just fascinated by the interrelationships between technical practices. The way that a "good" practice can become "bad" (and vice versa) depending on the working context can be very hard to figure out. Testing would be anot
1388.
by adrianhoward 15y ago
Agree completely. The first thing I thought when I read this was that it was going to be talking about the old extreme programming adage of YAGNI ( http://en.wikipedia.org/wiki/You_aint_gonna_need_it ) - only to find that it came to the exa
1389.
by adrianhoward 15y ago
I like working with other developers. Other developers seem to like working with me. I very definitely have an ego :-) I've worked with some folk who don't seem to work well with the rest of the team. They certainly make things unpleasant f
1390.
by adrianhoward 15y ago
If anybody on the team can spend a month going down a rabbit hole rewriting code then there's something seriously wrong regardless :-) The "Don't rewrite code without consultation" was the only one of Jeff's points I would niggle with. I
1391.
by adrianhoward 15y ago
>"I used to look up to Alan Cooper (who wrote _The Inmates are Running the Asylum_, where _the inmates_ are developers) but now I just loathe him. Programmers get a lot of unwarranted heat for producing unusable interfaces or producing
1392.
by adrianhoward 15y ago
One of the things that I do is help designer/UX folk understand developers better (and vice versa). There's a fascinating little exercise that I do that involves showing folk some screen mockups and getting people to write down the importan
1393.
by adrianhoward 15y ago
Interesting that you want to get rid of the support calls and e-mails. I'd hate to have to do that. I get so much useful feedback on what I'm doing wrong :-)
1394.
by adrianhoward 15y ago
Curiously enough my personal best-ever development experience was with exactly the 90m regular pair switching talked about here where we paired the most/least experienced on particular stories. It was brilliant. Great fun. Energising. Hugel
1395.
by adrianhoward 16y ago
I'd say yes - with B2B too although the sales pitch is different. You're usually dealing with somebody a couple of levels removed from the person using the product, and the usability benefits need to be emphasised more clearly - since they
1396.
by adrianhoward 16y ago
No. That really isn't the issue that I see at all. I've used Haskell's QuickCheck. Declarative testing is lovely. But it's one particular approach to testing - suitable for finding a class of problems and bugs. TDD via an xUnit framework is
1397.
by adrianhoward 16y ago
By and large the legacy problem isn't because Perl is a bad language per se - but because it's and old language (in popular usage). Old code in _any_ language tends to be bad. Popular languages especially since popular languages attract mor
1398.
by adrianhoward 16y ago
I too have the opposite experience :-) With something like Dancer the simple stuff is just as neat as playing with Sinatra/Ruby - with CPAN to pull upon for large chunks of functionality and a wonderful testing environment. Much as I love r
1399.
by adrianhoward 16y ago
Folk should also take a look at Catalyst http://www.catalystframework.org/ , Dancer http://perldancer.org/ and Jifty http://jifty.org/ - they're all nice to work with. Dancer being my current fave :-)
1400.
by adrianhoward 16y ago
Glad to see the book - and it looks a good read. Perl really has evolved as a language & community over the last few years and it's still my go-to language for my own projects. Despite having been mostly Python/PHP on the dev side the
1401.
by adrianhoward 16y ago
Those are all common well known UX practices. It's true many startups don't use them. In my experience this is usually because they don't have the in-house skills or knowledge. They don't have to be complex or expensive in time or money. Co
1402.
by adrianhoward 16y ago
Just one point on Cooper and the Inmates book... it was written 11 years ago. Cooper being a vaguely smart guy has learned stuff since then and has quite a different view on the way development and ux folk fit together now. Folks interested
1403.
by adrianhoward 16y ago
Catalyst == larger community + more documentation + lots of useful modules out there. The downside is that it takes a heck of a lot of effort to get up to speed and I personally find that it can get in the way a little for smaller projects.
1404.
by adrianhoward 16y ago
I wrote this http://use.perl.org/~Adrian/journal/33295 a few years back on how to not write job adverts. I still mostly agree with it :-)