I have a blog! Usually, it's photos from traveling or "how I made this" or "how I do this" kinds of posts. Basically, if I get tired of people asking me about something, I turn it into a blog post ๐
Probably the most interesting thing from it is the long-ass series of posts describing how I made my music album:
Mmm it sounds like you're using it in a very different way to me; by the time I'm using an LLM, I generally have way more than a general feel for what I'm looking for. People rag on ai for being a "fancy autocomplete", but that's literally what I like to use it for. I'll feed it a detailed spec for what I need, give it a skeleton function with type definitions, and tell the ai to fill it in. It generally fills in basic functions pretty well with that level of definition (ymmv depending on the scope of the function).
This lets me focus more on the code design/structure and validation, while the ai handles a decent amount of grunt work. And if it does a bad job, I would have written the spec and skeleton anyways, so it's more like bonus if it works. It's also very good at imitation, so it can help to avoid double-work with similar functionalities.
Kind of shortened/naive example of how I use:
/* Example of another db update function within the app */
/* UnifiedEventUpdate and UnifiedEvent type definitions */
Help me fill in this function
/// Updates event properties, and children:
/// - If `event.updated` is newer than existing, update as normal
/// - If `event.updated` is older than existing, error
/// - If no `event.updated` is provided, assume updated to be now()
/// For updating Content(s):
/// - If `content.id` exists, update the existing content
/// - If `content.id` does not exist, create a new content
/// - If an existing content isn't present, delete the content
pub fn update_event(
conn: &mut Conn,
event: UnifiedEventUpdate,
) -> Result<UnifiedEvent, Error> {
100%. As a solo dev who used to work corporate, I compare it to having a jr engineer who completes every task instantly. If you give it something well-documented and not too complex, it'll be perfect. If you give it something more complex or newer tech, it could work, but may have some mistakes or unadvised shortcuts.
I've also found it pretty good for when a dependency I'm evaluating has shit documentation. Not always correct, but sometimes it'll spit out some apis I didn't notice.
Edit: Oh also I should mention, I've found TDD is pretty good with ai. Since I'm building the tests anyways, it can often give the ai a good description of what you're looking for, and save some time.
Looks like polygon api can get live data 5/req a minute? https://polygon.io/pricing
I'm not super familiar with finance lingo; how is a "stock price" usually determined? ~~SMA?~~
edit: seems like "last quote" or "last trade" are probably the best for this kind of thing? https://polygon.io/docs/rest/stocks/trades-quotes/last-quote Those apis cost money, though. ๐ญ