Hacker News: rpep

New comment by rpep in "GitHub is no longer independent at Microsoft after CEO resignation"

rpep — Mon, 11 Aug 2025 18:21:57 +0000

I think there’s some risk with this though too - more and more is behind the enterprise tier. People try to work around this in various ways but its an unsatisfying experience. For e.g. trying to enforce merge request approval with pipeline stages.

New comment by rpep in "Go is a good fit for agents"

rpep — Mon, 09 Jun 2025 19:32:07 +0000

In practice the library ecosystem is just way behind Python. Maybe after you’re trying to optimise once you’ve worked out how to do stuff, but even the Langchain Go port is wayyyyy behind.

New comment by rpep in "Coventry Very Light Rail"

rpep — Sun, 08 Jun 2025 05:36:11 +0000

I live in a city with trams in the UK and that’s not how it works. There are sections that run on dedicated train lines, and sections where it runs on the street. Where it runs on the streets, priority is given over cars by switching traffic lights to red. Once the tram has passed onto the road it switches back to green so you can end up following the tram in your car.

New comment by rpep in "Marching Events: What does iCalendar have to do with ray marching?"

rpep — Fri, 18 Apr 2025 07:48:51 +0000

Much of that depends on country for usage.

In the U.K. when handwriting I think dd/mm/yyyy is much more common than dd.mm.yyyy

New comment by rpep in "US Administration announces 34% tariffs on China, 20% on EU"

rpep — Thu, 03 Apr 2025 06:58:09 +0000

Other thing is that when you’re VAT registered, as a buyer of parts you reclaim VAT on things you purchase as inputs. So the tax on the final product is what matters.

With US sales taxes you accrue tax all the way up the chain.

New comment by rpep in "BBC – Organizing music for organic discovery"

rpep — Tue, 25 Mar 2025 22:08:00 +0000

It’s interesting because BBC Sounds replacing iPlayer Radio was one of the worst redesigns I’ve ever seen for discoverability. Even now, several years on, it’s considerably worse. Whatever the technical merits of the migration, finding radio programmes became much much harder, all while they push podcast content.

New comment by rpep in "Show HN: I made a site to tell the time in corporate"

rpep — Mon, 24 Feb 2025 21:36:24 +0000

lol, yep, mine is 1st October?!

New comment by rpep in "MongoDB acquires Voyage AI"

rpep — Mon, 24 Feb 2025 21:34:15 +0000

You cant use the embeddings/vector search stuff this refers to in self hosted anyway, it’s only implemented in their Atlas Cloud product. It makes it a real PITA to test locally. The Atlas Dev local container didn’t work the same when I tried it earlier in the year.

New comment by rpep in "UK's hardware talent is being wasted"

rpep — Tue, 21 Jan 2025 06:29:59 +0000

Australia’s economy is propped up by the export driven mining industry. It’s not really a fair comparison.

New comment by rpep in "UK's hardware talent is being wasted"

rpep — Tue, 21 Jan 2025 06:26:19 +0000

> working for Rolls Royce in the middle of nowhere

Most people I know who ended up at RR live in Nottingham or the Peak District and commute in to Derby. Appreciate that’s perhaps not as exciting as London but it’s hardly a shit hole up here.

Agree on pay though. I work for a different engineering conglomerate (foreign owned) and I applied for a HPC role at RR a couple of years ago and the salary was £20k lower. The disparity would be even more now.

New comment by rpep in "UK's hardware talent is being wasted"

rpep — Tue, 21 Jan 2025 06:14:29 +0000

I’m 33, in the U.K. and my marginal tax rate is currently 66.7%, because the support you get for having children gets withdrawn between £60000 and £80000. If a promotion came up I would take it but it’s also at a point where I’m considering already dropping down to four days a week because of this. I don’t live in London so my life is very affordable. Save myself money on children’s nursery for a few years too…

https://taxpolicy.org.uk/2024/03/10/infographic_marginal_rat...

New comment by rpep in "SymPy: Symbolic Mathematics in Python"

rpep — Wed, 28 Feb 2024 16:42:24 +0000

I used it for this during my PhD: https://github.com/rpep/fmmgen and found it very powerful.

I have in the past used Mathematica, which I did think was more powerful for symbolic math to be honest, but it had the downside of not being free...!

Go First Impressions

rpep — Mon, 26 Feb 2024 09:30:24 +0000

Article URL: https://rpep.dev/posts/go-likes-dislikes/

Comments URL: https://news.ycombinator.com/item?id=39509226

Points: 1

# Comments: 0

New comment by rpep in "Origin of correlated isolated flat bands in LK99"

rpep — Tue, 01 Aug 2023 07:25:56 +0000

There are linear scaling DFT codes but they’re not available under open source licensing, only a strange license:

https://onetep.org/

New comment by rpep in "Ask HN: Could you share your personal blog here?"

rpep — Wed, 05 Jul 2023 06:07:48 +0000

https://rpep.dev/posts/alpine-python-antipattern/

https://rpep.dev/posts/improving-python-performance-numerica...

https://rpep.dev/posts/best-practices-django-views/

Have just been starting this really. Any feedback much appreciated.

New comment by rpep in "Django Views – The Right Way"

rpep — Fri, 16 Jun 2023 07:29:00 +0000

It depends on how much you want to rely on Mixins and using Serializer classes to do more than just serialise JSON. Neither of those are compulsory to use, and the more you lean into them the more inheritance you’re forced to do as soon as you need to customise the behaviour.

New comment by rpep in "Reddit’s blackout protest is set to continue indefinitely"

rpep — Fri, 16 Jun 2023 07:21:18 +0000

Bonds are much less risky too. So when interest rates were low, it made sense for investors to put money into companies because with bonds you got a tiny return guaranteed vs a high risk but potentially large payoff.

Now, bonds are guaranteeing a 5%+ return, so a non-profitable business is much less attractive as a proposition.

New comment by rpep in "Django Views – The Right Way"

rpep — Sun, 11 Jun 2023 10:12:10 +0000

ModelManagers are directly coupled to one model though. You mix concerns if you need to reference other models in them.

For e.g. say you have a User model and a corresponding “Profile” model. If you need to create the profile object when the user is created, it doesn’t really feel appropriate to put that in a UserModelManager directly coupled to the User object. This is the example given from the Hacksoft Django style guide to advocate creating a service layer.

In terms of the abstraction, I totally agree and tend to be pretty pragmatic about this sort of thing.

New comment by rpep in "Django Views – The Right Way"

rpep — Sun, 11 Jun 2023 06:41:44 +0000

CBV doesn't require you to do anything in particular other than implement retrieve/list/etc. methods on the GenericViewSet as needed, and get/post/etc. on GenericAPIView. You can use the convenience methods in Django and mixins, but as soon as you get beyond a simple case, they start to become a hindrance.

The only thing beyond that that I'd recommend is specifying a get_serializer_class method since it simplifies your boilerplate and plays well with drf-spectacular for generating your API documentation. I generally don't use ModelSerializer unless the logic is very simple, I've been meaning to write a blog post for a long while about avoiding it when your data model is split across two database tables.

New comment by rpep in "Django Views – The Right Way"

rpep — Sun, 11 Jun 2023 06:32:26 +0000

I disagree with the idea of not having a service layer at all, because in practice, changing your data model in some way is actually pretty common, even if the API remains the same so the data coming in/out isn't changing. I've had to split models into multiple parts to add audit history on certain fields, create notifications on object creation or modification (possible but hard to follow and a visibility problem when using signals), change the normalisation on fields, etc. etc. and at this point, turning to a service layer is much more appropriate than putting methods on the model since often the data is split across multiple database tables. I also would advocate this in projects where it's Django + DRF since you generally want exactly same logic to be run through whether submitting via a form or submitting via an API.

I've also found that it's good practice to impose boundaries between apps so that they are not strongly coupled together but communicate through an interface. That way, if you need to split an app out into its own project at some point, the migration is significantly easier from a code perspective, since the implementation of the interface function is all that needs changing on the consumer side.