Minerva is here! We've been working on this in the background for the past few weeks since decided to shut down. TL;DR: We are making RAG easier by helping you integrate GDrive (and other sources), chunking them, and embedding them for you.

@TheBlockChainer When I read the first line I was hoping you’d say sometimes you move it up only to realize you’re too lazy at the moment and move it back down in 5 minutes which I probably do half the time when I move mine up, lol

@0xnirlin The idea of rent is cool tho, imho

@sjkelleyjr It’ll be a great day when this happens

@pxue @davidnix_ Double damn

@davidnix_ Damn

> I can't have it make bigger changes than you'd like to see/review in one, maybe 2, atomic commits. I'll caveat or add to that: part of why I say that is because I think you should actually review it all and not just do "vibes coding". I find "vibes coding" to become a hellish mess quickly.

@StaffFind > Lots of contact mgmt tools to get that info. Like Apollo and the like?

Recently I had to mentor someone on the importance of git hygiene. In an ideal world commits should be singular in purpose, the messages should be descriptive, the history in the feature branch should be linear and overall clean. Git hygiene is important! It helps make code review easier. It helps pinpoint where you've introduced errors. But sometimes you work with teammates who may have not learned git commands or practices well. Or maybe they simply got in the habit of not caring about this. They may do commits that are not singular. Or maybe, hell, they might merge from main to feature-branch instead of rebasing (which imho creates a huge mess). And it's important to mentor them and to nudge them in the right direction, especially being the lead. But you also can't expect them to change 180 degrees in an instant. It will take them time... Time that you sometimes just don't have. Imagine you're on a two month long project with a team of freelancers. All are good devs, but half don't do proper git hygiene. Sure, over the next 6 months if you keep working together you could help them improve. And you should give them feedback even now. But more importantly right now is hitting that goddamn deadline and keeping the client happy. Git hygiene (and proper engineering in general) is important, but not as important as shipping the project. I think the most important skill of a good engineer/lead is pragmatism. Learn to accept that in the real world engineering won't ever be ideal. Nudge it in the right directions sure, but accept 80/20 solutions like (in my case here) squash merging so that the messy git history is hid away.

RT @benhylak: if o3 was the 175th best programmer in the world, every company in the world immediately stop hiring software engineers. we…

@SergioRocks Mech eng and CAD is also an interesting one

@packyM I feel like anyone that's tried to do any real work with AI knows that it's far from replacing us or killing us or whatever. And for anyone throwing a "bUt It WiLl ExPoNeNtIaLlY iMpRoVe"... you don't know that for a fact and you don't know how that will look

@charliermarsh `main` all day cause with python you're not always making an app. Very common to make a script, CLI, a lib or all sorts of other things. I think in JS land `app` makes sense, but not in python land.

@rakyll Also needs to lower and simplify taxes imho.

@davidnix_ @rezmos1 Agent is fun when it works and a mess when it doesn’t 😅

@0xMert_ I pace a lot in my office, so I'd say yes

@pxue Are you turning my pains into tweets? 😭

@AasthaAndani I don't think I know how to code by hand from scratch anymore even in langs I've used for years. I can edit existent code. But I think entirely in pseudo-code now.

Solana has its faults, but I think the concept of rent for storing data is really cool and it solves the infinitely growing state problem.