lawrjone

8 ms·

61.
by lawrjone 3y ago
They’re normalised histograms so the y axis is deliberately adjusted so you can compare the shape of the distribution, as the absolute number of builds in each bucket means little when there are a different count of builds for each platform
62.
by lawrjone 3y ago
Sorry you read it like this! If it’s useful: Pete wasn’t really being combative with me on this. I suggested we should check if the M3 really was faster so we could upgrade if it was, we agreed and then I did the analysis. The game aspect o
63.
by lawrjone 3y ago
I mentioned this in a separate comment but it may be worth bearing in mind how the AI pipeline works, in that you’re not pushing all this data into an LLM and asking it to produce graphs, which would be prone to some terrible errors. Instea
64.
by lawrjone 3y ago
Yeah there’s a large body of research that shows faster feedback cycles help developers be more productive. There’s nothing that says you can’t have fast feedback loops _and_ think carefully about your code and next debugging loop, but you
65.
by lawrjone 3y ago
I totally agree with your suggestion, and we (I am the author of this post) did spot-check the performance for a few common tasks first. We ended up collecting all this data partly to compare machine-to-machine, but also because we want his
66.
by lawrjone 3y ago
The build events track the files that were changed that triggered the build, along with a load of other stats such as free memory, whether docker was running, etc. I took a selection of builds that were triggered by the same code module (on
67.
by lawrjone 3y ago
Yeah everything you just said is exactly why we care so much about a great local environment. I've not seen remote tools approach the speed/ease/flexibility you can get from a fast local machine yet, and it makes a huge diffe
68.
by lawrjone 3y ago
Fwiw I've spent my whole career doing data analysis but the ease at which I was able to use OpenAI to help me for this post (am author) blew me away. The fact that I can do this type of analysis is why I appreciate it so much. It'
69.
by lawrjone 3y ago
That's interesting you saw less of an improvement in the M2 than we saw in this article. I guess not that surprising given the different compilation toolchains though, especially as even with the Go toolchain you can see how specific s
70.
by lawrjone 3y ago
Thank you, really appreciate this!
71.
by lawrjone 3y ago
Our team frequently work when travelling or from home, where they'd prefer not to have a desktop station. They also have an on-call rota where they need to respond to incidents remotely: I'd rather not chain my on-callers to their
72.
by lawrjone 3y ago
When you travel a fair bit for work or support WFH environments, I think it should cater for that, right?
73.
by lawrjone 3y ago
Yeah, I thought it was really cool! (am author) It's pretty cool how it works, too: the OpenAI Assistant uses the LLM to take your human instructions like "how many builds is in the dataset?" and translate that into Python co
74.
by lawrjone 3y ago
1. That was assuming 8 hours of regular usage a day that has GCP's sustained use discounts applied, though not the committed usage discounts you can negotiate (but this is hard if you don't want 24/7 usage). 2. The issue with
75.
by lawrjone 3y ago
Ahh right, I'd seen a few comments about the memory bandwidth when it was posted on LinkedIn, specifically that the M2 was much more powerful. This makes a load of sense, thanks for explaining.
76.
by lawrjone 3y ago
Yes I actually did the maths on this. If you want a GCP instance that is comparable to an M3 Pro 36GB, you're looking at an n2-standard-8 with a 1TB SSD, which comes out at $400/month. Assuming you have it running just 8 hours a d
77.
by lawrjone 3y ago
If you're using an Intel Mac at this point, you should 100% upgrade. The performance of the MX chips blows away the Intel chips and there's almost no friction with the arm architecture at this point. I don't use VSCode but mo
78.
by lawrjone 3y ago
Go on, I’ll bite: why?
79.
by lawrjone 3y ago
This is pretty much aligned with our findings (am the author of this post). I came away feeling that: - M1 is a solid baseline - M2 improves performance by about 60% - M3 Pro is marginal on the M2, more like 10% - M3 Max (for our use case)
80.
by lawrjone 3y ago
I’m not sure this would work well for our use case. The distributed build systems only really benefit from aggressively caching the modules that are built, right? But the majority of the builds we do are almost fully cached, having changed
81.
by lawrjone 3y ago
Author here, thanks for posting! Lots of stuff in this from profiling Go compilations, building a hot-reloader, using AI to analyse the build dataset, etc. We concluded that it was worth upgrading the M1s to an M3 Pro (the max didn’t make m
82.
Ask HN: Any good 2023 retros out there?
6 points by lawrjone 3y ago|1 comments
83.
by lawrjone 3y ago
Got a good discussion about this on LinkedIn for those interested: https://www.linkedin.com/posts/peterejhamilton_a-few-weeks-a...
84.
by lawrjone 3y ago
Thanks! We had a lot of fun putting it together.
85.
by lawrjone 3y ago
Am the author of this post :) Had a lot of fun trying to scientifically answer the question of "should we upgrade our MacBooks?" and using OpenAI to do the analysis, which was a first for me. Hope people enjoy it!
86.
by lawrjone 3y ago
I don’t have too much an opinion on either side here, but as a developer who works full time in Go (and has for >6 years) all these things exist in Go. Uncaught exceptions -> panics, like what this nil catcher is aiming to solve Place
87.
by lawrjone 3y ago
Enjoyed reading this job spec https://github.com/OneUptime/interview/blob/master/software-...
88.
by lawrjone 3y ago
Author here, just realised someone posted this to HN! Been using these types of abstractions for years and seen how much the benefits compound over time. Happy to answer any questions if you have them.
89.
by lawrjone 3y ago
I'm the author of the article. I 100% agree. Go's the language I use but I can't bring myself to love it!
90.
by lawrjone 3y ago
Mine is https://blog.lawrencejones.dev/ I’ve been working as a software engineer for about a decade now, primarily at startups. Recently the first employee at incident.io, before then working at GoCardless. Tend to write ab

More ›