David Oladapo

248 posts

David Oladapo banner
David Oladapo

David Oladapo

@oladapodev

Software Engineer intern @edu_tams Believe in yourself :♧

Ogun, Nigeria Se unió Temmuz 2022
576 Siguiendo108 Seguidores
Tweet fijado
David Oladapo
David Oladapo@oladapodev·
Built a personal writer agent. It has Quick, Research, and Deep modes, Quick: fast drafts, edits, and normal writing help. Research: source-backed answers with tool steps and citations. Deep: longer research loop for planning, comparing sources, and turning findings into stronger drafts. context linking from my blogs/projects/artifacts, chat skills with support if installing skills from @vercel skills.sh or GitHub folders organization of chats multiple model support and artifacts: saving chat message from me or the AI to be used later all @Cloudflare worker
English
4
3
29
2.8K
David Oladapo retuiteado
Insizwa
Insizwa@__Insizwa·
@demigodHITR @oladapodev I think either should be fine. 216 is just not mantainable. Fundamentally, I think what’s wrong with the approach here is the data modelling. Like a good use of role based auth, internal only operations that map to any tenant and even ditching rest for graphQL or RPC.
Insizwa@__Insizwa

@tomilola_ng 216 is a lot. Perhaps you need to simplify your data models? Throw in some form of claim based auth for user group distinction and I think you can reduce the number of endpoints. Theres some core data in here and some that’s just purely in memory or DB state.

English
0
1
1
22
David Oladapo retuiteado
Insizwa
Insizwa@__Insizwa·
@tomilola_ng 216 is a lot. Perhaps you need to simplify your data models? Throw in some form of claim based auth for user group distinction and I think you can reduce the number of endpoints. Theres some core data in here and some that’s just purely in memory or DB state.
English
0
1
3
513
David Oladapo retuiteado
Emmanuel
Emmanuel@ez0xai·
so rather than insulting or dragging someone over their architecture choices, it's better for us as software engineers to ask questions, understand the reasoning, and maybe learn something from each other just my two cents
English
0
1
1
235
David Oladapo retuiteado
Emmanuel
Emmanuel@ez0xai·
my point is that it's his system. He designed the architecture before building it, so I'm sure there was reasoning behind the decision i've built APIs like this many times and have successfully used both patterns depending on the use case.
English
1
1
0
254
David Oladapo retuiteado
Emmanuel
Emmanuel@ez0xai·
it would result in unnecessary db queries and data being fetched when only account details are needed on the other hand, if all that information is displayed together on the same screen, grouping them into a single endpoint could be a good design choice
English
2
1
1
294
David Oladapo retuiteado
Emmanuel
Emmanuel@ez0xai·
for example, it doesn't make much sense to return account details, followers, and following from a single endpoint if those pieces of data are displayed in different parts of the application
English
1
1
1
313
David Oladapo retuiteado
Emmanuel
Emmanuel@ez0xai·
he can also have a single endpoint that returns all of that in one response object, and that's valid too at the end of the day, the right approach depends on the business requirements, the application flow, and how those endpoints will be consumed
English
1
1
0
466
David Oladapo
David Oladapo@oladapodev·
😅 It's not like that. I never said having only 10 total endpoints will DDoS anyone. What I said was that one dashboard loading 10 different requests could cause problems or compute cost when you get more users This approach will be hard to scale. He then cited articles from Google and Microsoft which is fine for this companies because this companies have scale and compute to do that. Also Manageability also matters one clean POST with a JSON body is simpler than multiple small endpoints for things like profile updates. I would like to be wrong on this, but it still doesn't make sense to me.
Titanium@akinkunmi

That nigga really said you're going to DDoS yourself with 10 endpoints. 😂

English
0
0
1
26
Titanium
Titanium@akinkunmi·
That nigga really said you're going to DDoS yourself with 10 endpoints. 😂
English
3
0
21
2.7K
Zinny 🎀
Zinny 🎀@Zinny_Edmund·
As a Developer, can you cook?
English
12
0
15
402
David Oladapo
David Oladapo@oladapodev·
@jpschroeder It doesn't make sense for them to buy Cloudflare and they cant atm cause they're losing money
English
1
0
4
5.2K
Justin Schroeder
Justin Schroeder@jpschroeder·
OpenAI is going to buy Cloudflare.
English
156
39
1.3K
339.9K
David Oladapo
David Oladapo@oladapodev·
@rauchg @andrewqu Using this already 👍 x.com/i/status/20627…
David Oladapo@oladapodev

Built a personal writer agent. It has Quick, Research, and Deep modes, Quick: fast drafts, edits, and normal writing help. Research: source-backed answers with tool steps and citations. Deep: longer research loop for planning, comparing sources, and turning findings into stronger drafts. context linking from my blogs/projects/artifacts, chat skills with support if installing skills from @vercel skills.sh or GitHub folders organization of chats multiple model support and artifacts: saving chat message from me or the AI to be used later all @Cloudflare worker

English
0
0
2
692
Guillermo Rauch
Guillermo Rauch@rauchg·
Shoutout to @andrewqu founder and CEO of skills.sh 😁 you can just ship things
Andrew Qu@andrewqu

A few weeks ago I silently released the skills[.]sh API with "email me" instructions on the docs Since then, my email inbox has received >1200 requests for an API key I didn't want to keep generating API keys via script, but also didn't want to build a brittle "sign in experience" just for API keys Happy to see another beautiful use for short-lived credentials that come out of the box with Vercel!

English
4
2
60
12.3K
David Oladapo
David Oladapo@oladapodev·
@andrewqu Am already using this here x.com/i/status/20627…
David Oladapo@oladapodev

Built a personal writer agent. It has Quick, Research, and Deep modes, Quick: fast drafts, edits, and normal writing help. Research: source-backed answers with tool steps and citations. Deep: longer research loop for planning, comparing sources, and turning findings into stronger drafts. context linking from my blogs/projects/artifacts, chat skills with support if installing skills from @vercel skills.sh or GitHub folders organization of chats multiple model support and artifacts: saving chat message from me or the AI to be used later all @Cloudflare worker

English
0
0
3
544
Andrew Qu
Andrew Qu@andrewqu·
A few weeks ago I silently released the skills[.]sh API with "email me" instructions on the docs Since then, my email inbox has received >1200 requests for an API key I didn't want to keep generating API keys via script, but also didn't want to build a brittle "sign in experience" just for API keys Happy to see another beautiful use for short-lived credentials that come out of the box with Vercel!
Vercel Developers@vercel_dev

The skills​.sh API is now generally available. Power your agents, applications and platforms with access to over 600,000 skills ↓ vercel.com/changelog/the-…

English
9
3
63
25K
Austin
Austin@IamAroke·
The most overused word in tech? Scalable. Your app has 12 users, calm down.
English
39
7
193
8K
Titanium
Titanium@akinkunmi·
I wonder what the next crazy world event is going to be.
English
10
2
47
2.7K

Descubrir

@demigodHITR @tomilola_ng @akinkunmi @Zinny_Edmund @smartnakamoura @jpschroeder @rauchg @andrewqu