2,806 karma · joined December 13, 2012
thomasalwyndavis at gmail dot com @ajaxdavis on x
Is there a reason why Python has taken this long to get a mature alternative to "requirements.txt"?
Does anyone know why/how it maintains state if you tab out? Does Chrome eventually try to clean up the cache or is it locked in?
What the author could have done, and what I should have (but didn't) also, is add a bunch of possible values (enums) for each possible field value. This should solve it from coming up with variations e.g. node, nodejs
In zod/tooling it would look like this; remote: z.enum(['none', 'hybrid', 'full']), framework: z.enum(['nodejs', 'rails']),
But this just shifts the problem further down, which is now you need a good standard set of possible values. Which I am yet to find, but I'm sure it is out there.
On top of that, I am working on publishing a JobDescription.schema.json such that the next time the models train, they will internalize an already predefined schema which should make it a lot easier to get consistent values from job descriptions.
- Also I tend to forget to do it a lot recently in LLM days but there are plenty of good NER (Named Entity Recognition) tools out there these days, that you should run first before making robust prompts
* Willing to relocate: Yes - Australia
Technologies: Mostly Javascript. I've coded in pretty much all non functional languages though. Most of the databases sql/nosql. Comfortable with gCloud/aws/heroku etc. Mostly worked with node/rails/laravel/python/golang backends.
* Résumé/CV: https://registry.jsonresume.org/thomasdavis
* GitHub: https://github.com/thomasdavis/
I'm a full stack web developer who can build apps from the ground up. I've worked mostly at startups so I am used to wearing many hats. I am a very product focused developer who prioritizes user feedback first and foremost. I'm generally very flexible when investigating new roles. Nothing too big or small.
But gpt-4o actually got a working solution in a couple prompts -> https://gist.github.com/thomasdavis/fadbca01605fb3cb64911077...
Though the new artefacts is really damn handy, you can describe the most detailed projects, and it does a really great job of what you asked for, and I found it delivered beyond what I wanted.
I am now paying for both -.-
- it's hard to rank which codes better, but I think claude has better abstractions
- sometimes I paste the output of the other, and continue solving on the other
Awesome work, good luck!
Essentially, your whole blog is just one file called "resume.json" that describes where all your post/pages come from, they could be external or local resources linked -> https://github.com/jsonblog/jsonblog-cli/blob/master/blog.js...
And then you have "generators" which are just functions, that can take your blog.json and output all the required html/assets to build it e.g. https://github.com/jsonblog/jsonblog-generator-boilerplate
The main idea being that you only ever have to keep safe your blog.json, which you could put as a gist or anything.
Love your setup so far, will follow along.
It's insanely hard (nigh impossible?) to debug an aging app that has use useEffect's and useState's everywhere. (This wasn't the case with the class components (not suggesting that class components were the be and end all))
Now the Compiler sounds nice, and sure there is going to be a lot less code. But, at what cost, it does sound like it's just more magic, moved further and further into the React internals. Which I think unfortunately gives the developer less understanding and power.
I'm just ranting, it's not like the React lib itself is yet entirely divorced from it's principles circa half a decade ago, but I fear it may. Perhaps, they could promote and support more sub packages of React itself e.g. rendering, state
Thanks!
The module aspect is super cool, is there much adoption with any other projects using the individual modules? e.g. a webparser using the dom module
I'm probably going to open source a llm-structured-data-merge-thingy library (that has different merge strategies) in the near future.
---
My useful feedback;
- I thought the UX was broken when there was no next button after answering questions
- It would be great if the homepage showed a real example (real JD, real before and after)
- There was a bug in my upload (Thomas Davis pdf if you are looking at the database). It hallucinated a whole job I've never had into my finished resume.https://registry.jsonresume.org/thomasdavis/letter
https://registry.jsonresume.org/sadimfinity/letter
prompt/code: https://github.com/jsonresume/jsonresume.org/blob/master/app...
So you would turn on Frankens worker mode to sit on top of Laravel Octanes workers?
My understanding is that Franken keeps the app running so Laravel wouldn't need to restart anyway?
Why would you run both?
Fun and instantly understood.
2025 might be the right time.
If anyone wants to network and try build a relationship for potential co-founders shoot me an email. (profile)
I've got lots of ideas and can code almost anything.
Wikipedia has a lot of tables so I was wondering if content-aware sentence chunking would be good enough for Wikipedia.
In my mind that was the last hurdle to cross before being able to fool people regularly with a non-human voice.
Great work!
Hook that DSL into a prompt, [uv_break]gg. [laugh]
"From fixing prod to local dev..." ?????