David Oladapo

251 posts

David Oladapo banner
David Oladapo

David Oladapo

@oladapodev

Software Engineer intern @edu_tams Believe in yourself :♧

Ogun, Nigeria Beigetreten Temmuz 2022
572 Folgt108 Follower
Angehefteter Tweet
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
3K
David Oladapo retweetet
Precious Grace Egbewale
Precious Grace Egbewale@Graciecreatives·
I didn’t know my laptop was hacked when I’m always seeing my terminal open and closing itself until it almost ruined my job. I lost almost all my socials, I lost my X account, Discord, my IG and even my LinkedIn of over 2 years. That’s how I decided to start all over again 😪
Precious Grace Egbewale tweet media
English
22
2
60
1.1K
Theophilus Opoku Bannor | Shopwice
@Graciecreatives Some of you think your tech field is so special that it automatically makes you special. It doesn't. Skills may get you hired, but attitude determines how long you stay. No matter how talented you are, arrogance, poor teamwork, disrespect, and unprofessional behavior can quickly
English
4
0
0
54
Precious Grace Egbewale
Precious Grace Egbewale@Graciecreatives·
I would never work with a startup or anyone without signing a contract agreement. Earlier this year, I worked with a startup as a frontend developer (volunteer role) and when we’re almost done developing the UI, we were dismissed and removed from the repo 😂
Precious Grace Egbewale tweet media
English
19
0
43
1K
David Oladapo retweetet
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
35
David Oladapo retweetet
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
530
David Oladapo retweetet
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
245
David Oladapo retweetet
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
263
David Oladapo retweetet
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
308
David Oladapo retweetet
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
331
David Oladapo retweetet
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
496
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
31
Titanium
Titanium@akinkunmi·
That nigga really said you're going to DDoS yourself with 10 endpoints. 😂
English
3
0
21
2.8K
Zinny 🎀
Zinny 🎀@Zinny_Edmund·
As a Developer, can you cook?
English
12
0
16
430
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
6
5.8K
Justin Schroeder
Justin Schroeder@jpschroeder·
OpenAI is going to buy Cloudflare.
English
184
44
1.6K
423.5K