paulhallett

I’m working on a tiny terminal config / dotfiles / tool installation manager so I can keep everything in sync between my machines. Also includes profiles so I can tailor each machine how I see fit. https://github.com/phalt/pauldot

It’s intended just me for and follows a philosophy around hyper personal software that I’ve been developing: https://paulwrites.software/articles/hyps/

I agree. I’ve noticed this phenomenon too as I’ve been building more and more tools for myself, and I’ve started calling it hyper personal software: https://paulwrites.software/articles/hyps/

The irony is at the time of me writing this; gas is down to 4.6%[^1] and renewables are a whopping 88.5% and yep - the cost is based on the 4.6% of gas.

^1 https://grid.iamkate.com/

For a start, it doesn't have to be a replacement. You can progressively add it in. I work at a very very large organisation with a multi-million line codebase and we splash htmx here and there where it is useful (and where a full blown SPA would be too much to set up). We don't have to ditch any other FE tooling in favour of htmx - htmx "just works" nicely alongside everything else.

I like this idea, but this is suffering from too many buzz words that it's almost too difficult to understand. Embalmer, Curse, Archeologist? There's some pretty thin analogies to draw from. This won't make the system easier to understand, and it might actually affect adoption.

I once heard about a team that rebuilt a whole suite of micro services using names from Lord of the Rings, but the names didn't reflect the service's functions at all, so the system was instantly unusable due to the confusing terminology.

Keep the terminology simple.

I quit about six months ago. The majority of people I followed, I felt obligated to follow, in order to keep ahead of social issues. But the toll of "doom scrolling" constant negative/angry/depressed posts really hammered my own mental health. I also developed a habit of refreshing the feed on my phone every five minutes.

I quit, and I found myself lost when I picked up my phone, like a lingering habit (I see someone mentioned it being similar to quitting smoking).

On reflection, I think the reason I felt an obligation to keep up with social issues etc, was because I was using my real name (ironic that this HN account is also my real name!). I felt like I had to show I was caring and keeping track of it. I do wonder, if I create an account without my real name, I can just use it how I like, and maybe it will be a different experience.

It's slipping and sliding faster and faster. I'm keen to see the end of this stupid episode in history. The plant has so many positive and environmentally-friendly uses that it is completely absurdity to keep it banned.

You should add Māori names too.

Here is a resource with years worth of popular Māori names: https://smartstart.services.govt.nz/news/baby-names

It's always worth remembering that you can have an impact and still eat red meat. Cutting out meat on two or three days a week makes an impact. Most of my non-veggie friends treat meat like a treat, and only eat it on weekends.

This is the second place in Aotearoa New Zealand to be given this status, the first being Te Urewera. The NZ government grants these rights due to their Tapu for the Maori people.

https://en.wikipedia.org/wiki/Te_Urewera

Do they all talk at the same time?

The frame shift drive in the ELITE video game series is based on this technology: https://www.reddit.com/r/EliteDangerous/comments/2nqtzp/fram...

Django is the only web framework where I see consistently positive discussions about it on HN.

Bravo Django, and congratulations on another release!

Protip: ignore the docs on the website, use the docs on the github package / in the examples instead. They're much better!

Up until 90 minutes ago the previous change to this was 8 months ago. Before that it was 4 years ago.

I think you might be complaining about out of date documentation :)

Given django's docs are impressive, I doubt this is used actively by people.

Django in 2018 is still a very vibrant and active community. The project is actively developed, there is a lot of sponsorship from big companies (instagram etc) funding a dedicated fellow who's job is to work on Django full-time.

The plugin ecosystem is very rich and active too - almost always a pre-made package for some feature or implementation you want to add to Django.

Well, don't forget this is written by a man know for drumming up sensationalist products like the Indie Phone (crowd funded but never delivered, try google it), pissing off people, and even becoming a meme - https://imgflip.com/memegenerator/29521388/Indie-Phone-Aral-...

So the fact there is hyperbole is par for the course.

This is almost the exact opposite view of the London I see.

Isn't this just coffee lounges?

We (Lyst) recently shared our code review guidelines on GitHub:

https://github.com/lyst/MakingLyst/tree/master/code-reviews

We've tried to find a balance being keeping momentum and making sure you're shipping good quality code.

We've been using Python 3 since we implemented a new service architecture and it's been an easy transition for our 50+ engineers.

This post directly targets an individual in the PHP community and not the CoC in question. I'd suggest renaming this post as misguidance, irregardless of which side it is from, isn't addressing the point.

I think we've encountered another situation where developers who don't fully understand HTTP best practices and standards, are asked to adapt their internal API services to work on the web :(

All the methods that need to append `add`, `delete`, `update` to the URI. Why aren't you just using HTTP methods for this?

Why do I have to POST everything? Do you know what POST is supposed to be used for?

Deprecating an API is a bad way to go, especially if the API is fairly new. This post is telling me two things:

1) Dropbox's API was not designed correctly the first time. It should not just be a representation of their internal stuff exposed publicly. It needs to be designed first. 2) Dropbox is struggling to understand the difference between providing a consumer product (like their normal Dropbox product) and a developer product, like this API.

Oh wow you were there? Thanks!

Local caching will be the way to go.

All resources will have a "date_updated" or similar attribute which you can check against.

This is mostly just a typo in the examples I put, but I will consider using only strings for this type of stuff, to avoid issues.

Bloody markdown and no spell checker. I rely on them far too much, thank you

Oh that's a good point. Do I want my data to be consistent with the 1997 releases or the originals!?