HNHacker News
TopNewBestAskShowJobs

james_s_tayler

2,220 karma · joined October 30, 2018

submissionscomments
james_s_tayler··on Reddit confirms $300M Series D led by China’s Tencent at $3B value
I put in so many things to filter out politics. Still inundated with it.
james_s_tayler··on Microsoft: 70 percent of all security bugs are memory safety issues
Are you absolutely certain of that conclusion?

I'll agree with the sentiment that memory safe languages are less prone to security holes because by nature they entirely remove a whole class of issues related to managing memory...

but I can't help but think that it still stands to be the case that finding and patching the remaining holes that aren't related to memory management would still break the economics.

Perhaps the one thing I could imagine that might make a difference is regulations coming into force that mandated pentests / fuzzing for companies producing software doing a certain amount in revenue. It's been my experience that that stuff gets done but it's once in a blue moon. And stuff is always turned up. I'm yet to work anywhere where it is part of a regular process.

Even if it were I'm always blown away by security researchers who spend months and months attacking something and finally crack it then give a presentation about how they did it. There can't even be that many people on Earth with the level of skillset required.

I dunno... the economics of it seem to play out like "let's just deal with the fallout of an incident when it happens because that's cheaper than investing in security"

The asymmetric nature of finding holes vs not creating them combined with the asymmetric nature of the business value of investing in security is just a mildly awful combination.

james_s_tayler··on Microsoft: 70 percent of all security bugs are memory safety issues
Computer security is a fundamentally asymmetric game. Your entire stack needs to contain zero mistakes and an attacker only needs to find one. Also the resources you would expend trying to find and patch every last hole would break the economics. It is what it is.
james_s_tayler··on Many Americans Feel Cheated by Their Student Loans
Part of human nature. Same is true to varyingly degrees around the world. Research on deception/cheating is pretty damning of the people in general.
james_s_tayler··on Developers Are the Problem, Not Monoliths
Yup. The author does have some OK points in places, but some of them are either (a) facts of Life or (b) organizational/management issues.
james_s_tayler··on Developers Are the Problem, Not Monoliths
"my methodology works until management breathes down my neck but so be it!

"My methodology works until junior devs show up and don't know how to code"

"My methodology just works... except all the times it doesn't and when it doesn't, it's your fault because you did it."

That's what I got from this article.

It's development itself that's the problem. Software is really complex and things take a long time to build. The relationship between the time it takes for management to say "build it" and to actually build it is asymmetrical. It requires many people to build things of significance. Coordinating understanding of things between people is a hard problem. Gaining the experience to know why you should or shouldn't do something takes years. During that time you have to be working on things and contributing to code bases.

james_s_tayler··on None of my projects want to be SPAs
Re: long-term maintenance

So far every way of doing UI I have seen isn't maintainable long term. Yet somehow things wind up being maintained even if it is in that "why me?" kind of way.

I think this says less about frameworks/libraries themselves and more about the amount and sources of entropy present in the front-end. That's really what we're dealing with here.

Libraries/tools/patterns/frameworks all usually have the function of containing some of that entropy. In theory the best tool contains the most entropy while allowing you to produce results you can sell to all stakeholders.

I think over the years we are doing better and better, but it's a long game. We're not all the way there yet, is it even possible to get all the way to the dream?

james_s_tayler··on None of my projects want to be SPAs
GWT ouch. Or as I call it "get with the times!"
james_s_tayler··on 38% of bugs at Airbnb could have been prevented by using types
Depends on compile/deploy times really. 5 minutes per cycle is painful. 30 seconds not so much. You often just compile the part you need and that can be very fast. Depends on the language too. I've found .NET turnaround times faster than Java for example.
james_s_tayler··on 38% of bugs at Airbnb could have been prevented by using types
When writing in Ruby the "what the hell is this object I'm dealing with here and what methods does it have available?" Tax is like 320% for me. I love Ruby. It's so much fun and it's just neat in general but I find it much more taxing than a nice statically typed codebase I can navigate and reason about with ease.

Everything is just taxed differently. No such thing as duty free programming.

james_s_tayler··on Ask HN: How you ever quit because the engineering culture is too messed up?
Culture comes from the top. That culture is busted. The fact you can spot problems and solutions plus you care enough to try is a big indicator you're far better off in a culture that will utilize your mindset much better.
james_s_tayler··on On Being a Principal Engineer
This is one thing I consider as a criteria. Will it make a good story?
james_s_tayler··on On Being a Principal Engineer
I've been doing this starting this year. It's magic.
james_s_tayler··on On Being a Principal Engineer
This. This really is the value add and it's unique to every company, so it just takes time to learn.
james_s_tayler··on On Being a Principal Engineer
Supply and demand?

When you are employed they demand you show up every day and you supply yourself. There isn't an expectation that you wont supply yourself. After you leave but before you are hired back then there is demand but no supply. Leverage I guess. Makes sense to me.

james_s_tayler··on Strangler pattern, a powerful simple concept to do refactoring
Yeah. I'm really torn on this approach. I guess there aren't really any "good" options to redoing 3 years worth of stuff, so it's mostly an exercise in trying to pick the most acceptable bad trade-off.

The downside of this as I've experienced it is the tech-stack bifurcates and it becomes harder to ramp up new people. Or only some people get to work on the new shiny stuff and others just don't.

It's probably the best approach if you can guarantee the frankenstein won't persist forever. I've seen it get several frankensteins deep. At that point you're never getting rid of it, and the problem compounds. But there are no right/wrong answers, it's all completely context dependent and perhaps that's the only configuration in which the company can survive.

I also think there are likely certain inflection points in terms of project size/complexity. If the whole thing would only take 3 months to re-write then that's probably a good option. If it would take 3 years, it's probably not feasible. You know what I mean? The software itself is an input into the function of 'can we move this to a new techstack/architecture?' and I feel like there are certain parameters which have a safe operating envelope within which it's workable to do a re-write and not have the old solution hang around, but outside that the parameters may just simply not allow for it as a possibility.

james_s_tayler··on Strangler pattern, a powerful simple concept to do refactoring
Yes. Because brand. I discovered awhile ago now that the text isn't what sends the message. Who it's coming from sends a lot of the message.
james_s_tayler··on Strangler pattern, a powerful simple concept to do refactoring
A big piece of enterprise software I've worked on did a full rewrite successfully. This was a long time before I joined, but the original product was written in Magik and apparently the only requirement was "make it work like magik" which I thought was pretty funny. It definitely was a success.

Though on the same product I came across a mildly hideous half-baked attempt at a UI framework re-write. I got the story on that and it was definitely one of the time-wasting regret stories.

Software is mostly just hard and expensive.

james_s_tayler··on Strangler pattern, a powerful simple concept to do refactoring
hahahah oh man. That's such a trap. Good point.
james_s_tayler··on Rules for Choosing Nonfiction Books
So what you're telling me is that I didn't read the guidelines. Kind of my point exactly. But anyway.
james_s_tayler··on Rules for Choosing Nonfiction Books
Given someone always has rare first hand experience and this is true for all stories that would actually mean no news stories are actually true.

Probably an accurate statement really.

james_s_tayler··on Rules for Choosing Nonfiction Books
Hmm so better to just overtly state "you didn't read the post."

?

james_s_tayler··on Moving from Go to PHP Again
Totally agree with this.

The way I think about it is if you think through the entire software stack and all the instructions that get executed across all the machines and their operating systems and programs running underneath before things even get to your code and then all of the standard library and framework code plus your code. For just a simple loading a web page that is a trillion piece jigsaw puzzle and every single piece has to line up or the whole thing just doesn't work.

We do the humbling and the remarkable every day and trillion piece jigsaw puzzles are no joke. It's the exception that you get it right. Given all the pieces required that's a lot of sources of potential entropy and the more it increases the more the system destabilizes and/or becomes unworkable. Things like languages, libraries, frameworks etc make certain decisions on your behalf with the goal to contain some of that entropy within their given abstraction.

james_s_tayler··on Moving from Go to PHP Again
Well let's not pretend software is an engineering discipline.

It's art, fashion and politics.

james_s_tayler··on Tell HN: Wells Fargo completely offline
People are also advised to leave the room before the fire takes effect.
james_s_tayler··on Why are we templating YAML?
I find XSLT intolerable in practice. Thankfully I've only had to touch it a handful of times. I agree the idea behind it is neat but boy is it a headache.
james_s_tayler··on Ask HN: Developers aged 50, how have you gotten around age discrimination?
I'd be impressed by that. Like who does that? Especially if it was these days. That'd be inspirational.
james_s_tayler··on Ask HN: Developers aged 50, how have you gotten around age discrimination?
There's a good course on Pluralsight about learning management strategy. It basically boils down to considering the expected half-life of the knowledge and then apportioning time based on that and stratifying the learning.

I can't recall the specifics but it's something like

  10% deep-diving on long-lived fundamentals
  25% going deep on your core stack you will be using for the foreseeable future
  The rest on the what's in front of you + what's coming next
I really like it.
james_s_tayler··on Ask HN: Developers aged 50, how have you gotten around age discrimination?
What actually ends up happening is people like you make outlandish truth claims about the dispositions, aspirations and futures of strangers on the internet who they have no context for. And get it it oh so wrong.

People often misconstrue my pragmatic hyper-realism for pessimistic defeatism. It's nothing of the sort.

Nice rhetoric though! I really pictured the rotting corpse at the computer in the basement of the fortune 10 and partying on the beach with models and bottles making the promo video for Fyre festival. You really took me there.

james_s_tayler··on Ask HN: Developers aged 50, how have you gotten around age discrimination?
I'm glad we're on the same page.
← PreviousPage 33 of 34Next →