vicnastea.io
Fun - Techno House Niners Syrah
Work - Principal PM Netflix App Dev Platforms
Argentino 🇦🇷
me.vic.dev
151 posts
1,761 followers
764 following
Regular Contributor
Active Commenter
comment in response to
post
You may prefer the analysis from @redmonk.com redmonk.com/sogrady/2024...
Looking forward to the next one being published.
comment in response to
post
Awesome! Thanks for the pointer.
comment in response to
post
Spring AI is jam packed.
When will we see an RC? Asking for some friends…
comment in response to
post
Nice!
What system did you land on for organizing them in the drawers?
comment in response to
post
comment in response to
post
comment in response to
post
Very!! 😐
comment in response to
post
What it's purpose is?
comment in response to
post
Fun to watch! Keep on cookin!
comment in response to
post
RE: rate limits I've advanced to the highest tiers without requiring me to "Contact Sales" and even have hit the limit on my work accounts a few times.
I'm starting to think that getting better at the specification is the real unlock for the workflow I want.
comment in response to
post
I've been using it to test the limits (no pun intended) of prompting workflows to create features on increasingly larger code bases.
At this point a lot of the work on my end is figuring out the proper size of feature to have it implement and how detailed and specific I need to be in my prompts.
comment in response to
post
Are you looking for something like Goose which allows you to use your own provider keys AND add your own tools easily?
To me, this was the Swiss Army knife I was looking for.
My biggest hurdle at the moment is rate limiting :/
block.github.io/goose/
block.github.io/goose/docs/t...
comment in response to
post
Great idea!! Did add this to your .goosehints?
comment in response to
post
bsky.app/profile/vicn...
comment in response to
post
I wanted to use internal documentation as added context for various dev flows so I integrated our internal auth mechanism to pull down the raw HTML then convert it to Markdown to hand back to the LLM.
The coolest part was that when getting the first page it took note of other links it could follow.
comment in response to
post
comment in response to
post
They hold a certain gravitas.
comment in response to
post
Almost sawed off my feet at the ankles.
comment in response to
post
comment in response to
post
comment in response to
post
/subscribe
comment in response to
post
I feel this in my bones.
comment in response to
post
😂😂😂😂😂😂😂😂😂😂😂
comment in response to
post
A tweet for you, by you.
comment in response to
post
This why they pay you the big bucks to innovate @puerco.mx!!!
comment in response to
post
I’m leaning there too.
@thock.in has the iconic caricature.
comment in response to
post
Will do an A/B test 🤣
comment in response to
post
There is no official project status of “not recommended” this is deprecation while supporting bug fixes for big customers IMO.
To your original point it’s likely the reason why it continues to use a deprecated library itself.
comment in response to
post
cloud.google.com/storage/docs...
comment in response to
post
This matches my understanding from when I was at GCP.
comment in response to
post
This sounds 100% correct