HNHacker News
TopNewBestAskShowJobs

james_s_tayler

2,220 karma · joined October 30, 2018

submissionscomments
james_s_tayler··on Ask HN: What people skills do you wish you learned earlier in your career?
When you wake - i'd love to read it too. I want to second the opinion that learning to build consensus is a very, very valuable skill. It's how a lot things really get done. I've never gone so far as to document things extensively or really need to, but it sounds like you learned some very interesting tactics on how to build consensus effectively because you were forced to. Not a fun position to be in, but if you could share the tips that would be valuable.
james_s_tayler··on How is it like to be a dev in Iran
maybe that totalitarianism is the default and that "freedom" is a recent development that has been very hard won. It is not the default state of things. If you lose it i.e the state becomes totalitarian, it is orders of magnitude harder to go back the other way.
james_s_tayler··on Tell HN: Docker just ate 19GB of production data
I agree with both of you. It's not helpful to not know the context and the op wasn't necessarily in control of it. But at the same time if you are someone in control of the context (which you aren't really if you are a line level employee) you should be aware this is a bad pattern. If you are a line level employee and this is being imposed on you for some reason or other you should sound an alarm if you know to "hey, for the record - this is a monumentally bad idea - just saying".

I've seen plenty of stuff in my career where I've gone on record to say "hey - we really shouldn't do this". Nothing got done about it. But hey, I did what I could.

Recently I learned about Rasmussen's dynamic safety model. I think this is a very handy mental model to have. It's the human factors that make what we do really hard. Often line level practitioners know better than they are allowed to do in practice and trying to fight organizational politics to Do The Right Thing can be an uphill battle.

james_s_tayler··on In the Defense of Spaghetti Code (2013)
I think it's useful if you have a rule at the outset of a project that rejects things longer than X where X is the 99% percentile length of a method.

I ran the stats retrospectively on a codebase I once worked on to derive sensible values for max class length and max function length. To be honest, they came out at some fairly sensible values and I would be happy putting a blocker in place to say "if you are doing anything more than this, you shouldn't be". I think it was something like 200 lines for a method and 3 or 4 thousand lines for a class.

If you can do it at the outset what you'll find is that the vast majority of the time the rule is never triggered. In the majority of cases that it is triggered, it's trivially easy to break the method up a small amount to be under the limit. It's very, very rare to feel like you're having to break it up unnaturally and it feels very forced, though it happens on the extremely odd occasion. I'm OK with that trade-off. The benefit is you never wind up with the 5k line long methodzilla that someone thinks is a good idea and everyone laments forever.

Every code base I've seen has one godzilla method. I'd prefer we avoid godzilla methods at least. You don't need an 18k line class. Nor a 5k line method.

james_s_tayler··on Skills Poor Programmers Lack
Abstract Algebra makes it way into code sometimes...

https://mikhail.io/2018/07/monads-explained-in-csharp-again/

james_s_tayler··on Ask HN: What have the past 12 months taught you?
>Our four year old is twirling in circles as the paramedics arrive. She asks the cop if he can open her milk, she's thirsty

I teared up at this point. I've got a 4 year old and that is the exact kind of thing they do. Just kids being kids don't realize how even the most mundane, simple, innocent of their behaviors can be stress inducing at the easiest of times. Then they do the same things they always do but this time all hell is breaking loose and you're like "please, just don't".

james_s_tayler··on Ask HN: What have the past 12 months taught you?
A lot of the world is political and has its fair share of crazies. HN is a part of the world.
james_s_tayler··on Operating a large distributed system in a reliable way: practices I learned
The notion of a "root cause" itself is flawed. It's causes acting in concert which cause problems and they all enable each-other.
james_s_tayler··on Ask HN: How to deal with constantly getting cut off in work discussions?
I had a friend who was quite bad at doing that. I eventually made it known and together we worked on it. I can't imagine a whole company like that. It was hard enough to get one individual with which I had a solid relationship to stop that. Good news is he did get much much better and now it's no longer an issue.
james_s_tayler··on “10x engineers”: Stereotypes and research
We all do that stuff from time to time, but I rarely find someone who is consistently that bad in everything they do. I have seen them, but my point is they are also rare.
james_s_tayler··on “10x engineers”: Stereotypes and research
I'd say it's a combination of raw intelligence, passion and ability to see a vision of how things ought to be and bring it into being.

The people that stand out to me aren't necessarily the ones who do what they're told. It's the ones who do what's effective.

james_s_tayler··on “10x engineers”: Stereotypes and research
I tend to always see it within a single shop at least. Whether it's 10x or more like 3x is debatable but "significantly more productive" is usually obvious.
james_s_tayler··on “10x engineers”: Stereotypes and research
>A -10x engineer wouldn't be capable of creating anything from scratch, even if they did they would likely have issues getting buy in from the wider organization for said code to go into production

I have a two data points from a -10x engineer that say otherwise. They definitely do start things. The rest of us spend a decade making their mess a stable, workable system.

james_s_tayler··on “10x engineers”: Stereotypes and research
Agreed.

I think there is a bit of Dunning-Kruger going on too. The "architecture astronaut" variety always manage to introduce mountains of tech debt.

james_s_tayler··on “10x engineers”: Stereotypes and research
I think true -1x devs are also rare like 10x devs. To be -1x everything you "contribute" has to be a net negative. They are out there, but I think they're also rare.
james_s_tayler··on “10x engineers”: Stereotypes and research
I think there are different flavors of 10x. The people that I've worked with that I would consider to be of the 10x variety weren't the kind of 'trail of destruction' type that some people tend to talk about.

I worked with a guy, great engineer, great guy, deep domain knowledge and a very solid understanding all the way through the stack. He was a great mentor and only barked when he was absolutely too slammed to help, which was rare. The thing that always amazed me is not only did he consult on all the really difficult stuff and ship it, but frequently you would come back to code you wrote recently and it would look nicer, cleaner and just a little more polished. He'd been in there leaving not a trail of destruction, but a trail of cleaning.

Now, I have also heard of the trail of destruction kind too. They're more like -10x though. They just pump it out really fast, but super low quality. IMO that's a bad kind of 10x to be. It's 10x the recklessness. A truly great engineer is one that can help the team and the company avoid writing as much code as possible. As such I don't consider the 'trail of destruction' 10xers to be 10xers, but rather really fast cowboys.

james_s_tayler··on “10x engineers”: Stereotypes and research
I think this perspective is totally underrated. When I compare a lot of people's careers I see these dynamics jumping out at me a lot. Timing timing timing. Autonomy too. When you're decent at what you do and you're allowed to do it, it turns out you can do good things. When you do good things you get more of the right kind of experience. Gaining that experience is rare in the first place thus making you even more rare and valuable (in the right context).

I'm glad I'm not the only one out there that sees it like this.

james_s_tayler··on “10x engineers”: Stereotypes and research
>Part of the whole 10x package is getting the manager on board and increasing trust, not going behind their back.

It's a bit of column A and a bit of column B. Organizational politics often blocks productivity. Often the it's better to ask forgiveness than permission is quite effective so long as you're reasonably astute about how much political capital you have, how much you will make from the move and how much you will spend by the move. Other times it's the ability to build consensus and gain buy in to remove the organizational roadblocks is what can really be a force multiplier.

Both of these dynamics are at play.

james_s_tayler··on “10x engineers”: Stereotypes and research
That's how I read it to. I don't think he straw manned it??
james_s_tayler··on “10x engineers”: Stereotypes and research
Yeah. I find it an odd response. My assumption is it's normally distributed, so you'll find a sliver of people who just (for one reason or another) blow by the rest. You'll find a lot of average developers. You'll find a tiny minority of people who somehow wound up in industry and you can't for the life you figure out how they made it 15 years.
james_s_tayler··on Alan Cooper on the “10x” Programmer
Agreed. I've known some very productive, very stable, very nice engineers. I've met the erratic kind too, but they're definitely not all that way.
james_s_tayler··on What Happens to Spelling Bee Champions When They Grow Old?
amazing
james_s_tayler··on Developers don't understand CORS
Hahahaha. Hot damn. Oh that would really get my goat.
james_s_tayler··on Jeremy, I think you'll wan't this job
Yeah. If there is one thing I've observed over the years is that systems usually function as the design goal intended. So if you think the system is broken because the behavior is odd then there is a high chance you just misunderstood the design goal.
james_s_tayler··on Developers don't understand CORS
Git is amazing, beautiful piece of software.

But... sigh I feel exactly how you feel about Git about Vim. It's the one editor everyone has decided despite it's arcane and bizarre UX that you aren't a real programmer if you don't know.

Refuse to learn it. Absolutely refuse.

I think everyone has one of those things.

james_s_tayler··on Developers don't understand CORS
Anki
james_s_tayler··on How I Taught My Kid to Read
Children's books are usually horrible for learning foreign language. They're full of all sorts of cutesy bullshit that's really strange. Some children's books aren't but if you read a lot of them you find they actually often contain quite bizarre language and scenarios.
james_s_tayler··on Clear is better than clever
...I agree with your comments on Liskov Substitution Principle, that the fact it's even possible is a weakness in OOP type systems.

But the rest of your examples are very far off base.

I somewhat agree with Single Responsibility being perhaps not quite right as "single" isn't always desired, appropriate or possible. But the general philosophy is absolutely on point. It's an instruction to carefully consider whether a component should be responsible for something or not and if not then think about where else that responsibility should lie. It gets pretty gnarly when you see things that just have way too many responsibilities. They become unwieldy. An object being responsible for holding and manipulating its state isn't what I would class as a responsibility. That is below the line. That's thinking far too granularly about what a responsibility is.

Same for open/closed. There is a great picture that represents open/closed of a human body (being the closed system) that you can put different layers of clothes on (open for extension) which I think beautifully captures the essence of the principle. When this is done right it's an absolute blessing. You mostly find it in frameworks that have a life-cycle and at certain points (say before anything happens or after everything has happened) they provide an overridable method with no behavior. That method allows you to insert logic the framework designers didn't think to cater for, but also keeps the framework life-cycle intact.

The example of dependency inversion just doesn't make sense. If you're creating a string manipulation library it should take strings and nothing else. It doesn't need anything else. If you're creating a string manipulation library in the first place you probably should just use the standard library. Maybe that's just a bad example, but I still don't agree with your sentiment with always avoid runtime dependency injection.

Forgetting the string manipulation example - I'm curious what you have in mind when you say "modules should instead communicate with one another". How does this communication take place? What language are we talking about and what does some code look like? Mostly what comes to mind when I think of that are either newing up an instance of a class or calling a static method, or perhaps making some kind of http/tcp request?

james_s_tayler··on Clear is better than clever
> The compiler can tell if something isn't referenced - but it can't tell if a provider that goes into a DI framework is never invoked.

It sort of can though. It depends on the circumstance. If there is an interface with one implementation or even multiple implementations and that interface isn't referenced anywhere nor are any of its references then you can reason that those dependencies might be provided to the DI container but will never be requested as they can't be. In that case - delete them.

In the case where you have one interface which has multiple implementations and the interface is referenced, I agree. Nothing will tell you if there is one implementation sitting there entirely unused forever.

If you wanted to solve that problem you probably could. In practice I don't find it a big issue.

james_s_tayler··on Clear is better than clever
My favorite recently is a class named CustomerCommandMapEmbelisherConverter.

It's not a good name. Nor is it concise, informative or anything vaguely useful.

But I get the strong feeling it comes from someone spouting off a line along the lines of "we need to name things for what they do" and then someone else just coming up with that.

In your case I'm going to guess doBillCustomer() is about 2.5k lines long with a copy of its entire logic duplicated and it branches based on annual or monthly billing and subtle bugs have been fixed in one implementation but not the other and now they are diverged such that they are only 93% the same but that means all bets are off. There are 15 levels of nesting and it interacts with at least 5 external systems during all of that.

Am I close?

← PreviousPage 24 of 34Next →