If your customers are paying in USD or GBP, they shouldn’t have to jump through hoops to complete a purchase.
With Bumpa’s Paystack integration, Growth merchants can now accept USD & GBP card payments directly on Bumpa, giving international customers more ways to pay while making it easier for your business to sell beyond borders.
Whether you’re selling fashion, beauty products, services, or anything in between, accepting payments in more currencies can help you serve more customers and unlock more opportunities for growth.
Because the more ways your customers can pay, the fewer barriers stand between you and your next sale.
Log in to Bumpa and explore international payment options today.
#getbumpa #bumpaforbusiness #paystack #businessgrowth #internationalpayments
If you’re planning to study or work in the UK in the next few months,
this first version is for you.
It’s free until you actually need a human involved.
https://t.co/SGrXfDkkF2
Reply with “UK” if you want me to DM you the link and a short loom showing how it works.
I built something for people planning UK study or work who are tired of guessing.
Today, we’re launching @kinnrahq a way to test if your UK visa plan actually makes sense before you start spending.
https://t.co/SGrXfDkkF2
It takes 3 minutes!
Coming to Go from another language? Probably?
Here are 5 patterns to unlearn if you're coming to @golang from Java ... https://t.co/wI98EtEJ3x
And another opinion on how to format directories without overthinking it ... https://t.co/HA3M7JhGNB
Trick for me is to practice, what you think you already know i.e materials you have read, what you do at work, etc), what you want to learn.
I do this with my github at least
We used to ask candidates to build a particular stateful API from zero. You show up with your laptop and you’re given an empty folder, and can use the internet however necessary to accomplish it. (this is all pre-AI)
Startup engineers owned it, FAANG devs struggled.
The theory is that big tech engineers rarely if ever have do greenfield development. All your work is sandboxed within a framework that someone has already setup for you. You get routing, build tooling, logs, observability, database connections, CICD, for free, and those muscles either never developed or have atrophied.
The conflicting signal was that the big tech engineers were then considerably better at large systems design than the startup folks, and we had to tweak the whole process to get better signals.
Hard agree. The problem is that .NET devs love the make everything general purpose even though most of the time these extensions are only used in one file each where they should have been a function.
The obsession to make everything general purpose is because that’s what they are being taught by the .NET team who suffers from the same syndrome.
Want to implement a health check? Let’s make a general purpose framework for it.
Want to write light weight HTTP handlers? Let’s make a framework for it.
Want to load config values from environment variables? Of course that requires a framework.
Want to manage dependencies? Frameworkzzzz yolo.
Want to validate the Authorization HTTP header? NoT wHiThOuT a FrAmEwOrK
The answer to everything is a general purpose function and a framework in .NET.
“So you learned Blazor instead of React, is that right?
“yes Dave”
“Just so you can build internal business apps for that ungrateful HR group for the rest of your career?”
“that’s correct Dave”