HN user
Aider is in development for almost 2 years now. Publishing another tool that "offers significant improvements" will have to catch up first.
Having options is a good thing, and approaching the dev agent problem space from a different perspective will help with pushing ideas in other products as well.
There's llms.txt [0], but it's not gaining much popularity.
My web framework of choice provides these [1], but they're not easily injected into the LLM context without much fuss. It would be a game changer if more LLM tools implemented them.
I've had the same thoughts on those. Maybe it also allows them to gather data on whether/how people interact with a webpage itself, which may be an indicator for its quality.
Have you seen https://text-to-cad.zoo.dev/ ?
But yes, there's a lot of potential and, in my uneducated opinion, low hanging fruits for 3D printing especially.
In addition to the initial loading time noted by the other posters:
You may want to use the same inference engine or even the same LLM for multiple purposes in multiple applications.
Also, which is a huge factor in my opinion, is getting your machine, environment and OS into a state that can't run the models efficiently. It wasn't trivial to me. Putting all this complexity inside a container (and therefore "server") helps tremendously, a) in setting everything up initially and b) keeping up with the constant improvements and updates that are happening regularly.
Yes, too much water on the beans can lead to water gathering on the burrs, which can lead to rust on the burrs.
I use the teaspoon method (just the handle), cover it in water and stir the beans a couple of times. Just a single data point, but I've done this for 2 years at ~2.5 shots a day with no sign of rust on the burrs. YMMV
Hey folks! I'm a motivated, generalist full stack software developer that builds on strong, practical fundamentals. I'm always looking to learn something new and expand my knowledge. I write software for more than 2 decades now, and currently focus on sustainable and accessible web development.
I'd love to find a remote position with a positive impact on the world, and a place where I can build awesome stuff with awesome people. I'd welcome a part-time position as well, if possible.
Location: EU, Germany (UTC+2)
Remote: Yes, preferred
Willing to relocate: No
Technologies: Full Stack, Svelte & SvelteKit, TypeScript / JavaScript, Go, Rust, .NET, Serverless & Edge (primarily Cloudflare)
Résumé/CV: https://fdumont.net/resume?token=46b88224280d42f489acb437e326adf6
Email: [see résumé]Hey folks! I'm a motivated, generalist full stack software developer that builds on strong, practical fundamentals. I'm always looking to learn something new and expand my knowledge. I write software for more than 2 decades now, and currently focus on sustainable and accessible web development.
I'd love to find a remote position with a positive impact on the world, and a place where I can build awesome stuff with awesome people. I'd welcome a part-time position as well, if possible.
Location: EU, Germany (UTC+2)
Remote: Yes, preferred
Willing to relocate: No
Technologies: Full Stack, Svelte & SvelteKit, TypeScript / JavaScript, Go, Rust, .NET, Serverless & Edge (primarily Cloudflare)
Résumé/CV: https://fdumont.net/resume?token=708e4b5d03524e88a201d9ab08e6c759
Email: [see résumé]I think it's eminently readable
This. And proper line breaks help a lot, too. There's a reason single line breaks are ignored.
People have mentioned tables here, and...yeah, they're messy, ...
IIRC, the "original" markdown does not include tables. They've been added by GitHub (I think), because it made sense for them, and many parsers started to adopt. I agree they are not easily readable in "source mode". It helps to properly align stuff, though, but it's a PITA.
These lanes and pull outs aren't common everywhere. When I visited NZ, it took me a day or two to realize they had a purpose. RVers usually are not driving in their home country.
I just recently tried to use the side lane in DK to let others pass (set signal, decelerate, pull over as far as possible). It actually confused the other drivers so much that they didn't dare to take over, even when there was lots of space to do so.
I'm in a similar position. Top x% in my field, more than fair compensation, somewhat financial security. I worked my butt off towards burnout to get there (currently slowly recovering).
I recently listened to a conversation between Lex Fridman and Stephen Wolfram [1]. Stephen said something that stuck with me for a while. Something along the lines:
GPTs are statistical word guessing machines. They regurgitate the average of the internet. You can get around that by placing with temperature and top-k, but that'll only make them less accurate, and increase the chances for them to hallucinate.
You, however, are an expert. Better than the average of the internet. Years of experience, and likely with higher standards. You understand the requirements, architect maintainable systems, and align with the company goals. You learned how to read requirements from context and between the lines.
Yes, GPTs can do highly complex things, and sometimes it feels magical or even scary. But you'll have to prime them to do so, and you'll have to guide them. They are your junior programmer, and you are their lead. You understand context, and they don't (simply because they don't have any).
Start to accept that from now on you have your personal junior dev. Learn to guide him into the right direction, and learn to provide accurate tasks. I'd also suggest looking into GitHub copilot chat to see where this is going.
If we're lucky, they'll get better with time and lots of research, but that's (likely) none of your concerns.
Uneducated opinion:
From this point on, I think it's likely the corpus they consume gets worse because they are starting to consume their own generated, average-of-the-internet content. You built your own Reddit bot, and know how easy it is to get generated content out there. It's a problem that isn't solved yet, and with time, it's becoming even more difficult because the number of different public models (which suffer from the same challenges) is steadily increasing, and therefore detection of such content gets a lot harder. The technology might get exponentially better, but in the end it boils down to the corpus they consume and learn from. This will slow things down, and will give you some time to learn to use these tools to your advantage, not see them as competition.
Very cool to see this indeed! I always had an eye on AstroNvim.
I'm currently on a slightly customized NvChad setup and am happy with it. It mainly transitioned me to lua configs, which has been a good decision.
How do you compare with NvChad? It's a slightly different set of tools, yes, but why did you think it needed another 'preconfigured vim' distribution?
They definitely have sensible backout mechanisms for their free tiers (i.e. Pages, they still serve static assets but disable compute/Functions). Also, their docs are written pretty well, and openly hint at dangerous price traps.
We launched a big presale this year with an e-commerce app hosted on Workers, and we just barely hit the 5$ threshold for the paid plan. Did not use more services (other than DNS/proxy) though, so YMMV.
Heck, 8k trees is a lot. Definitely find a professional. Growing coffee is exceptionally difficult.
Do you have an idea which crops have been planted? Is the plantation in a favorable location (altitude, weather)?
Depending on both, you should become clear about whether you want to produce commodity coffee or specialty coffee. The latter is more difficult to produce, but also more profitable.
If you're going the specialty route, it may even be fruitful (hah!) to get in contact with content creators. They usually have useful contacts in the industry, and they might be willing to connect you.
In any case, try to get in touch with European roasters, as they usually value traceability and prefer to roast single origin coffees.
Best of luck! And enjoy the journey.
Oh, and if you had your first batch, please drop me a message. I know a few local roasters (Germany) that may be interested in new sources. :-)
It is pretty fast for me in central Europe. Maybe it's latency?
Some people prefer a keyboard-focussed workflow and try to avoid using the mouse as much as possible.
When I first tried warp on my new keyboard, I really did not understand what was happening and thought it was bugged. The bindings came by default. I removed them and went on.
A few days later I wanted to add custom macros and had to read the docs. Skimming the warp section made me realize it's basically just recursive space positioning. I tried the mode again, and soon realized how incredibly useful this is.
It's a bit difficult for me to keep the state in my mind when going down the tree because there's no visual indicators. It's a keyboard firmware after all.
The marketing page is an absolute nightmare for me on the phone. It is laggy, some links simply do nothing (broken scripts? because the browser attempts no navigation at all), clicking the trade-in button only refreshes the page, and worst of all clicking on the pre-order button entirely crashes my browser.
What's happening there?
Sadly, this message was sent from my Pixel 6 pro, which I used to browse the product page.
My bad, this was meant to be a top level comment. Will be re-posting as such.
The marketing page is an absolute nightmare for me on the phone. It is laggy, some links simply do nothing (broken scripts? because the browser attempts no navigation at all), clicking the trade-in button only refreshes the page, and worst of all clicking on the pre-order button entirely crashes my browser.
What's happening there?
Sadly, this message was sent from my Pixel 6 pro, which I used to browse the product page.
on this blog, I want to thoughtfully embrace imperfection.
Jokes aside, yes it is a nightmare. However, you can find a transcript at the bottom of the page, which makes it a little more readable.
Can't go into much detail, sorry. But yes, we sell our own events as well as events for other organizers.
It's ironic that we only found out about the scale of automated traffic after moving to CF. Before, we were just fire fighting the load during peaks, while thinking our infra is the problem.
and has been scaming people in Switzerland
Same here. We issued a restraint order against Viagogo years ago, but still receive >30% 'automated traffic' during high demand pre-sales, according to Cloudflare.
Even though we put lots and lots of resources into making it as difficult as possible for black markets, it still seems to be a quick and easy way to make some cash.
From experience, the factor is more like 5-10. Depending on the complexity of the existing solution, and depending on the wealth of custom implementations, of course.
Because SAP is what most other companies in the sector use and because there are few alternatives. And because everyone else is m uses it, it must be good. Right? Right?!
Also, because leading employees usually have no idea about the intricacies of the "old" system and think it's easily replaceable with a solution from the shelf.
I really like the concept, good job!
Just a nitpick: I'd like to see the repo org or author in the repo listings. The top 20 is currently listing 3 different stable-diffusion repos with no obvious differences (except for the ranking scores).
This is awesome progress. Slicing is an incredibly hard problem, there's still so much to discover and I'm glad they do.
I'm trying to push the speed limits with my printer and Arachne helps tremendously. I hope it's being merged into Superslicer soon so we can have the best of both worlds.
Interesting! This is an issue I had with an external API which I intended to cache on my serverless workers infra.
I hit the API's rate limiter when the workers invalidated their cache, even though I staggered the lifetime of the cache keys for each replicated instance. This is how I found out how many Cloudflare workers run on a single edge instance. Hint: It's many.
Didn't know it had a name. I'm delighted, thanks!
I appreciate your actionism. This is one of the reasons I love HN - super tech savvy people helping each other out. Kudos.
Interesting read. I'm an emotionally unstable person, and perfectly aware of that. I've found my tools and mechanisms to handle that. But when COVID hit our company and my team and I had to cope with the changes in culture and environment, I could see the gradual increase of dissatisfaction, reduction of emotional energy, and stress that spread out to every single team member. Some could cope (by slacking 80% of their time), some couldn't, because they had to wear the slackers on their shoulders.
However, I was sure it wasn't just me who suffered. I could feel it hitting the others too, and we even openly talked about it. The job was still interesting, got more challenging and our impact on the health of the company grew. It felt nice, at least to me.
It wasn't big things that made us unhappy, but rather the small stuff. Annoyances, such as missing/stolen computer mice in the office, dirty floors or stale coffee beans in the machines.
The analogy with the 'pebbles' hit me hard.
_Maslach has affectionately named this feeling “pebbles.” She describes them as the tiny, incremental, irritating, and painful stuff at work that can wear you down._