I'm a freelance programmer in Brighton in the UK. I work in lots of languages but I seem to use Python and JavaScript the most. I spend most of my time working from a Brighton co-working space called The Skiff (http://theskiff.org/) which is very nice.
I was on Twitter @almostobsolete but who uses Twitter anymore?
Find me on Mastodon at @[email protected] or on Bluesky at https://bsky.app/profile/almostobsolete.net
Submissions
Petlibro: Pet Feeder Is Feeding Data to Anyone Who Asks
bobdahacker.com
7 points·by almost··1 comments
Tell HN: Stripe seems to have suspended human customer support
23 points·by almost··3 comments
US Broadband Speeds Jumping 90% Had Nothing to Do with Killing Net Neutrality
techdirt.com
37 points·by almost··6 comments
Postcard Sized Raytracer
fabiensanglard.net
3 points·by almost··0 comments
Native Apps in JavaScript with React Native [video]
vimeo.com
2 points·by almost··0 comments
Native Apps in JavaScript with React Native (slides)
almostobsolete.net
1 points·by almost··0 comments
Custom Native iOS Views with React Native
almostobsolete.net
46 points·by almost··13 comments
SQLite3 bindings for React Native
github.com
46 points·by almost··1 comments
Keepod: Can a $7 stick provide billions computer access?
m.bbc.co.uk
34 points·by almost··29 comments
Awesome chrome extension for people who hate the word "awesome"
github.com
1 points·by almost··0 comments
The fastest pulsar spins at 716Hz; its equator spins at 24% the speed of light
en.wikipedia.org
122 points·by almost··78 comments
Solving a Regular Expression Crossword with Haskell, Part 2: Representation
almostobsolete.net
9 points·by almost··0 comments
Solving a Regular Expression Crossword with Haskell, Part 1
almostobsolete.net
5 points·by almost··0 comments
Show HN: Simple email discussion lists.
listeron.com
9 points·by almost··5 comments
NebriOS - Business Process Management using Python Scripts
nebrios.com
1 points·by almost··0 comments
Videos shot from onboard the Space Shuttle's Solid Rocket Booster
io9.com
1 points·by almost··0 comments
Show HN: Where in the world are HN users? (will ask you to share your location)
head2.me
2 points·by almost··1 comments
Show HN: Find your friends with realtime (but temporary) location sharing
head2.me
8 points·by almost··6 comments
Generator (yield keyword) support in CoffeeScript for Node.js
For me Northflank have filled this spot. Though by the time I switched I was already using Docker so can't speak directly to their Heroku Buildpack support.
I've been incredibly happy with Northflank since moving over a few years ago after Heroku got unreliable. Felt like an upgrade from Heroku and the support and reliability have been great.
The reason you heard that was probably because they were talking about a more specific circumstance. For example SQLite is often used as a database during development in Django projects but not usually in production (there are exceptions of course!). So you may have read when setting up Django, or a similar thing, that the SQLite option wasn't meant for production because usually you'd use a database like Postgres for that. Absolutely doesn't mean that SQLite isn't used in production, it's just used for different things.
From my experience though I often do make logical errors in my code but not in my tests and I do frequently catch errors because of this. I think thats a fairly normal experience with writing automated tests.
Would having someone else write the tests catch more logical errors? Very possibly, I haven't tried it but that sounds reasonable. It also does seem like that (and the other things it implies) would be a pretty extreme change in the speed of development. I can see it being worth it in some situations but honestly I don't see it as something practical for many types of projects.
What I don't understand is saying "well we can't do the really extremely hard version so let's not do the fairly easy version" which is how I took you original comment.
This sounds very "the perfect is the enemy of good". Tests don't need to be perfect, they don't need to be written by different people (!!!), they don't need to cover 100% of the code. As long as they're not flakey (tests which fail randomly really can he worse than nothing) it really helps in development and maintenence to have some tests. It's really nice when the (frequent) mistakes I make show up on my machine or on the CI server rather than in production, and my (very imperfect, not 100% "done properly") tests account for a lot of those catches.
Obviously pragmatism is always important and no advice applies to 100% of features/projects/people/companies. Sometimes the test is more trouble to write than it's worth and TDD never worked for me with the exception of specific types of work (good when writing parsers I find!).
For something this simple that doesn't need to grow or interact with the rest of the system why would you need Backbone or React? And why would you expect any version to be shorter as it's mostly just the HTML and the data.
I remember writing Backbone applications with lots of deeply nested components. Trying to keep all the state in sync and reacting to events. It certainly wasn't simple and straightforward.
360 degrees in a circle predates Plato by quite a lot (2000 years I think!). It comes from the Summarians more than 4000 years ago. They used a method of counting on fingers that goes up to 12 on one hand and 60 using both hands, so their numbering system was based on 60. 360 is 6 * 60 and also roughly how many days in a year.
Later societies inherited that from them along with 60 minutes in and hour.
So it monkey-patches a set of common http libraries and then detects calls to AI APIs? Not obvious which APIs it would detect or in what situations it would miss them. Seems kind of dangeorus to rely on something like that. You install it and it might be doing nothing, You only find out after somethings gone wrong.
If I was using something like this I think I'd rather have it wrap the AI API clients. Then it can throw an error if it doesn't recongise the client library I'm using. This way it'll just silently fail to monitor if what I'm using isn't in its supported list (whatever that is!)
I do think the idea is good though, just needs to be obvious how it will work when used and how/when it will fail.
I haven't, but it sounds honestly really bad. Sounds like it sucks for everyone right now. I just think your product will make it worse, probably only very slightly worse but still worse.
Surely this now means now hiring managers (and people your code incorrectly identifies as hiring managers) now get spammed with loads of bullshit generated messages. Which obviously they'll ignore. But now you've made their jobs a bit harder by breaking a previously (maybe) working communication channel.
So you've put a effort in to build a product just to make the world slightly worse on net. Not hugely worse, but still it doesn't seem like the best way you could have spent your time.
This sort of article seems perfectly poised to be useless to beginners (no context, doesn't tell you how to use the things) and experts (no nuance, just listing basic features) alike. Who is it for? Why does it exist? Why is it posted here?
There are a finite number of names, and an even smaller number of good names. But apparently an infinite number of hacker news posters who comment on every new project to complain that the name has been used before for something else.
And even the fact that this is a fork of an earlier project and the name comes from that doesn't stop it!
(I'm aware I have chosen a very weird thing to be getting annoyed at over my breakfast crumpets this morning)
Weird that a gambling app would take thename of a popular character from legend!
Or maybe not, try actually naming something sometime and you'll see. It's not easy to come up with something that fits all the requirements AND has never been used before.
And it's not like anyone is ever going to get confused and accidentally try and use Dropbox's internal load balancer to buy options on a stock or something. Or try and make a gambling app the star of their next hit movie for that matter.
Coins used to be largely worth what they were worth because of what they were made of. So cutting them in half would lead to two seperate halves of the value. I'm sure there's more nuance than that but broadly I think that's how it used to work.
http://almostobsolete.net/ (Geeky website stuff) http://tomparslow.co.uk/ (Freelancer portfolio stuff)
I'm a freelance programmer in Brighton in the UK. I work in lots of languages but I seem to use Python and JavaScript the most. I spend most of my time working from a Brighton co-working space called The Skiff (http://theskiff.org/) which is very nice.
I was on Twitter @almostobsolete but who uses Twitter anymore?
Find me on Mastodon at @[email protected] or on Bluesky at https://bsky.app/profile/almostobsolete.net