This approach seems to be everywhere. But if you have a defined workflow, requirements, clear permissions, etc, it makes more sense to feed them to codex once and have it build a website that can be audited once and then runs deterministically. Code reuse is well understood if you want to build on past work. There's a large group of people who can't really do that, I know, but they shouldn't be building bots that have permission to edit anything.
I was expecting this to be the point of the article when I saw the title. Popular projects appear to be drowning in PRs that are almost certainly AI generated. OpencodeCli has 1200 open at the moment[1]. Aider, which is sort of abandoned has 200 [2]. AFAIK, both projects are mostly one maintainer.
[1] https://github.com/anomalyco/opencode/pulls [2] https://github.com/Aider-AI/aider/pulls
All the use cases that popped into my head when I saw this were around how nice it would be to be able to quickly see what was really happening without trying to flop between logs and the AWS console. That's really how I use k9s and wouldn't be able to stand k8s without it. I almost never make any changes from inside k9s. But yeah... I could see using this with a role that only has Read permissions on everything.
Thinking about this some more, maybe I wasn't considering simulators (aka digital twins), which are supposed to be able to create fairly reliable feedback loops without building things in reality. Eg will this plane design be able to take off? Still, I feel fortunate I only have to write unit tests to get a bit of contact with reality.
This is sort of why I think software development might be the only real application of LLMs outside of entertainment. We can build ourselves tight little feedback loops that other domains can't. I somewhat frequently agree on a plan with an LLM and a few minutes or hours later find out it doesn't work and then the LLM is like "that's why we shouldn't have done it like that!". Imagine building a house from scratch and finding out that it was using some american websites to spec out your electric system and not noticing the problem until you're installing your candadian dishwasher.
I was hoping Bash would go away or get replaced at some point. It's starting to look like it's going to be another 20 years of Bash but with AI doodads.
How fast is it?
I've never had that great of a memory. The upside is that you can have a bad memory and good note taking skills and be more effective than the 'good memory' people. Really it's just that I forget in a day what other people forget in a week so it's not that big of a gap. But some considerations:
1. Put everything in the issue tracker that you can. This includes notes on what actually happened when you did the work. Include technical details.
2. Try to push everyone else to use the issue tracker. Also makes you sound like the professional in the room.
3. Have a very lightweight note taking mechanism and use it as much as possible. I am gud at vim so I use the Voom plugin (which just treats markdown headings as an outline but it's enough to store a ton of notes in a single .md file). Don't try to make these notes good enough to share as that adds too much overhead.
4. Always take your own notes in a meeting.
5. I will revisit my notes on a project from time to time, and sometimes walk through all of them, but I'm not really treating them like flashcards to memorize. I'm just looking for things that might need some renewed attention. Same with the backlog.
6. In general, I don't try to improve my memory because I don't know what I need to know for a week vs. what I won't look at again for a year. So I focus on being systematic about having good-enough notes on everything and don't really expect to remember anything. (I do remember some things but it's random.)
And the implication is the 'quality' of engineers at the companies is actually reversed - the top performers at Dropbox are struggling and leaving while the under performers at FANG are struggling and leaving.
This looks kind of interesting. I might try this. Thanks.
Fair enough. Although that seems rather complicated for those of us just trying to get a quick cert for an internal host. The LetsEncrypt forums are full of this discussion:
[1] https://community.letsencrypt.org/t/whitelisting-le-ip-addre... [2] https://community.letsencrypt.org/t/whitelist-hostnames-for-... [3]https://community.letsencrypt.org/t/letsencrypt-ip-addresses...
Another nuisance is that unencrypted port 80 must be open to the outside world to do the acme negotiation (LE servers must be able to talk to your acme client running at the subdomain that wants a cert). They also intentionally don't publish a list of IPs that LetsEncrypt might be coming from [1]. So opening firewall ports on machines that are specifically internal hosts has to be a part of any renewal scripts that run every X days. Kinda sucks IMO.
[1]https://letsencrypt.org/docs/faq/#what-ip-addresses-does-let...
UPDATE: Apparently there is a DNS based solution that I wasn't aware of.
There are lots of simple things that are normally easier to do in the web framework that are suddenly easier to do in the database (with the side effect that you can do DB optimizations much easier).
But the other consideration is that you likely need to do a lot with a reverse-proxy like traefik to have much control of what you are really exposing to the outside world. PostgREST is not Spring, it doesn't have explicit control over every little thing so you're likely to need something in front of it. Anyway, point is that having a simple Flask server with a few endpoints running wouldn't complicate the architecture very much b/c you are better off with something in front of it doing routing already (and ssl termination, etc).
I'm on a POC project that's using PostgREST and it's been extremely fast to get a big complicated data model working with an API in front of it. But I guess I don't get how to really use this thing in reality? What does devops look like? Do you have sophisticated db migrations with every deploy? Is all the SQL in version control?
I also don't really get where the users get created in postgres that have all the row-level permissions. The docs are all about auth for users that are already in there.
That's what I want... this would force me to make a different account for every topic I might comment/post on, and they can have their own local networks. If it's a topic that I know a lot about (eg what I do at my day job), it would force a fresh start every few years.
This is in contrast to my twitter account, which is such a mess that I don't like posting b/c "most" people who will see it followed me for some other topic.
Ok but how do I know I should trust Cure53?
This is a research university that moves very slow, so waiting two years for something better is actually a possibility (and prerendering to S3 works ok for now). I'll keep this bookmarked.
Thanks, I hadn't heard of that and I will look into it. This is a research setting with plenty of hardware we can request and not a huge number of users so that part doesn't worry me.
This is on our list of possibilities. It would take a little more time than I'd like to spend on this problem but it would work.
How to make png encoding much faster? I'm working with large medical images and after a bit of work we can do all the needed processing in under a second (numpy/scipy methods). But then the encoding to png is taking 9-15secs. As a result we have to pre-render all possible configurations and put them on S3 b/c we can't do the processing on demand in a web request.
Is there a way to use multiple threads or GPU to encode pngs? I haven't been able to find anything. The images are 3500x3500px and compress from roughly 50mb to 15mb with maximum compression (so don't say to use lower compression).
My boss did UI/UX on Mosaic (we are both at NCSA today). I will ask her on Tuesday when I see her. She has lots of wild stories about why things are the way they are.
Looks really nice. The big blob of parameters in the kwargs looks pretty intimidating to get correct. Maybe consider a builder object for the config: https://en.wikipedia.org/wiki/Builder_pattern. It would probably be easier to document, too (document the setter methods of the Builder rather than try to explain the nested dict). Feel free to ignore me.
The nice thing about programming on a RaspberryPI is that the only websites that are light enough to use are Google, Stackoverflow, Github, ReadTheDocs, etc. If you try to check Reddit/Twitter/Facebook you get frustrated with how slow they are and go back to the text editor.
All it needs to be able to do is page-down or scroll-down and I want it (I have RSI problems in my hands).
Thanks for saying this ^^, it's the best explanation of what this thing actually is (sorry but I didn't really get it from the homepage). Define a state of infrastructure using a real sdk (not yaml files) and it can figure out and apply the migrations from the current state to the new state. (right?)
Except for occasional flare ups, mine is pretty much gone and at worst was pretty debilitating (eg hurt to pick up a glass of water). I think all of these do a lot:
- Exercises and stretches from the pdfs here: https://orthoinfo.aaos.org/. Finding some that feel kinda good and then doing them a few weeks worked better than suggestions from doctors. I do the exercises as part of my warmup for my normal 3x a week workout and do the stretches at the end.
- Use a stylus for my phone at all times. Just the type that is a ballpoint pen with a rubber tip on the cap. Also a pop-socket to hold it with.
- Cut down on bike riding for the sake of my wrists.
- Play mostly console games, less phone and PC b/c consoles have more ergonomic controllers.
- Fasting. I do at least a 24hr fast every week and that always works at least temporarily. I have several problems related to inflammation and for some people this helps a lot.
Geekiest bonus suggestion: use XFCE as a desktop and configure all the hotkeys so you can do things like move windows around with the keyboard.
I don't think it matters much b/c of the super low volume but I do have it behind Cloudflare free-tier.
This is correct. Why would I put any more effort into it?
I have my site in an S3 bucket with the static-site flag activated. It would not win for 'easiest'. However, it's the only thing in my personal AWS account right now and my monthly bill is $0.83
Index fund performance is starting to sound exactly like "house prices have never gone down" in 2005.