@TheDumbTechGuy My favorite approach, design DB use DB to generate data classes and interfaces, design API spec use that to generate server studs and API clients, now you can start the business logic and UI in parallel... schema driven development
@TheDumbTechGuy This is because of the [legacy ness] of core banking systems, think about it if the date of the txn is been used how will reconciliation be smooth.
Also to the core when the txn moves from pending to posted is can see that as a new activity and trigger a notification
@Akintola_steve@PsudoMike Java or .Net been used in the banking space has very little to do with the technical details(types and others). It's more of ecosystem, reliability (battle tested), security and most importantly legacy (most banking systems are old so consistency and easy integration)
@TheDumbTechGuy My take: if you are able to convince yourself you will need microservices in the future, start with modular monolith. In that future that might never come, just add proper devOps and you can get your dreamed microservices.
But always ask yourself if you need it 🙃
@Akintola_steve Microservices on the table again, sad when people always copy architecture with proper context. Burning company's revenue when one digital ocean droplet could have done the job.
In the end I think we fall in love with the tech so much that we forget why we are building it
For the past 6 years, we have documented the evolution of the African tech ecosystem from the front lines. Now, we are ready to cover yours.
Let’s make your next event a permanent part of the story.
Help us capture the pulse of Ghana’s tech scene
This anonymous survey gathers insights from all tech professionals to identify trends, gaps, and opportunities for growth.
Take the survey now: https://t.co/x2uqXHpJzh
Share with a techie & let’s to map the ecosystem 🇬🇭
I wrote about the three common types of Machine Learning and how they differ. Check it out here 👇
“From Data to Decisions: How Machines Learn in 3 Ways” by Audrey Zunuoh Ponu https://t.co/PgVg28zRVy
@TheDumbTechGuy@soulpee 2. The data in the Jwt is public(base64), so if you keep vital info there and the FE saves it (because he must use it in other requests until expired) you are exposing too much..
And more. Just read the OAuth 2.0 guidelines or explore JWE or PASETO
@TheDumbTechGuy@soulpee I think it's part of the state
And the jwt is not meant for the client to decode, because of a couple of reasons:
1. Normally the FE won't verify the jwt with the necessary key, so how do you confirm the jwt is coming from your actual BE. So a hacker the exploit the FE
Your heart’s sending error signals.🫀
Too much screen time💻, zero movement🏃♀️ = higher risk of cardiovascular diseases⚠️.
Touch grass at #CodeCup25.
Let’s move for our health🩺.
🗓 28th June | 📍 Wembley Plus
🎟 https://t.co/EqMAQdaJto
#CodeCup25
We still have player spots for designers, product and other techie teams for the upcoming Code Cup event on the 28th of this month at Wembley Plus, East Legon
Register to play now via https://t.co/9zYNQG2H1I
It’s a free to attend event, share with a friend 🫶🏽