I am a Software Developer with over 4 years of experience. I work with the following:
✅Typescript
✅React/NextJS
✅Express
✅PostgreSQL, MongoDB
✅Test Driven Development
✅Sequelize
✅Agile driven Dev
✅ShadCN,MaterialUI,TailwindCSS
Available for dollar based remote roles🤲🏾
Morning Devs, let’s do something that can promote ourselves today.
A Mini CV.
I am a Software Engineer with about 8 years of experience. I work with the following:
✅Typescript
✅React/NextJS
✅Express/NestJS
✅MySQL, PostgreSQL, MongoDB
✅ElasticSearch, Redis
✅Test Driven Development
✅Prisma, Sequelize,TypeORM
✅AWS,AzureDev
✅AgileDriven Dev
✅ShadCN,MaterialUI,FlowBite
Available for dollar based remote roles.
*RT and Quote with yours and i will RT.
@IhejirikaS48939 You cannot rubbish the competition and anticipate to win
I would love to see Portugal win after Mr. Ronaldo retires. In fact, I’ll support them to win
I FIND A BETTER WAY DEPLOYING NEXTJS APP ON MY VPS.
We were burning CPU, RAM, and ~10GB of disk on our VPS every deploy building a large Next.js app directly on the server.
So we changed the model:
Build on GitHub Actions → push to GHCR → Dokploy pulls and runs.
No more yarn build on production. Deploys went from 15–20 minutes (when they didn’t fail) to seconds.
What changed: → Server = run containers, not compile code
→ Same image from staging (:release) to prod (:production)
→ Rollbacks = pull a previous tag
→ Freed ~10GB from old BuildKit cache alone
Same app. Cleaner ops.
If your VPS is still building Docker images on every push, you might not need a bigger server — you might need a different pipeline.
added configurable color ink accents + thickness 🧑🍳
again, the difference with this is that the output timing matches 1:1 with your input (at 0.5x below)
still jus' css + svg 💫
@Akintola_steve Backend always have a good understanding of what is happening in the system when it comes to flows, infra, deployment etc
Even without them being the team lead, they automatically feel like boss to frontend devs at least