Deeluxify.design @deeeviny

First Illustrator practice piece done using shapes Can’t wait to learn more and see what I can create with Illustrator.

Designed this launch teaser for Settle, an AI powered debt tracking app. The goal was to create anticipation while keeping the design clean and on brand.

Clean. Minimal. Intentional. Designed this X header for @trysettledebt as part of its brand identity.

tired of "I'll pay you back" going nowhere building Settle, track who owes what, split bills, get reminders that actually work works offline. syncs when you're back online. no excuses for "I didn't see your message" launching soon

Another piece from the @trysettledebt identity project. This time, a feature showcase focused on clarity over clutter.

Lending money is easy. Remembering who owes who isn’t. I designed this brand campaign for Settle, a debt tracking & reminder app that helps you keep track of what you’re owed, what you owe, and sends gentle reminders so you don’t have to. Feedback is welcome.

keyboard_arrow_left Previous keyboard_arrow_right Next

Designed the identity for Settle, a debt tracking & reminder app. The symbol is built around a simple idea: a dot with notification rays. The dot represents something being tracked. The rays represent Settle’s gentle nudges. Just like a friend who’s good at remembering things.

A while ago, I shared the logo. Here’s what it looks like now that it’s live on the product. Designing brands is one thing. Seeing them become part of something real is another. Proud to have designed the identity for Complify

Deeluxify.design @deeeviny

2 months ago

Recently designed this logo for Complify, a platform that helps businesses stay compliant and organized. A custom-drawn C and checkmark come together to create a simple, memorable brand mark.

0 1 3 150 0

Settle is for: → the friend who always covers the bill → the one who forgets to pay back → friend groups splitting everything → roommates keeping score → anyone who hates the "hey, about that money" text If any of this resonates, let’s chat! 👀

keyboard_arrow_left Previous keyboard_arrow_right Next

Had fun working on this flyer for Tribal Chief Autos. I kept the design clean and modern with a subtle cultural touch to match the brand. Curious to know what you think.

Recently designed this logo for Complify, a platform that helps businesses stay compliant and organized. A custom-drawn C and checkmark come together to create a simple, memorable brand mark.

stop using JavaScript to compute layout contrast ratios you can now offload relative luminance math entirely to the browser using native contrast-color() and container style queries Check out this interactive, zero-JS auto-contrast card component: codepen.io/JudeIV/pen/OPW… v

Guess what I’m working on today🫠

I'm building a recursive walker that traverses nested map[string]any and []any structures (mostly JSON-like data). My current implementation works but involves a fair amount of code like: switch v := value.(type) { case map[string]any: // recurse case []any: // recurse default: // process value } As the walker grew more complex, I found myself adding more type assertions and branching logic than I'd like. I'm curious how others approach this problem in production Go code. Do you stick with type switches and assertions? Have you found a cleaner pattern using generics, interfaces, visitors, or reflection? At what point do you decide to unmarshal into concrete structs instead? Any lessons learned from building recursive traversals over arbitrary data? I'm not looking for a "one true way" but interested in patterns that have held up well in real-world codebases.

One of my recent projects Designed a banner and product sticker for a pancake brand, and seeing the designs come to life on mockups made the process even more exciting. Grateful to my first paying client for trusting me with their brand. More creative projects ahead.

keyboard_arrow_left Previous keyboard_arrow_right Next

When starting backend projects, start from the data and work outward. schema/data models first — You can't build anything meaningful until you know what your data looks like. Define your entities, relationships, and constraints. Everything else derives from this repository/data access layer — How does data get in and out of your DB? Get this right before touching business logic. Swapping an ORM or query later is painful services — This is where actual business logic lives. Write services against your repository interfaces, not against HTTP. A service shouldn't know or care if it's being called by a REST controller, a cron job, or a queue consumer controllers/routes last — Controllers are just thin translators: HTTP in -> call service -> HTTP out. If your controller has real logic in it, that's a smell. Move it to the service. Why this order? services tested in isolation catch bugs before you wire up HTTP your business logic stays reusable (REST today, gRPC tomorrow, no rewrite needed) controllers become so thin that they barely need testing

@StephanieInii Thank you Stephy

Worked on a cupcake menu animation using Canva, followed a tutorial but made sure I understood each step Used match and move transitions and some text effects to bring it together. Clean, simple, and a solid practice

And when it finally works out, don’t say I got lucky! I put in the work.

Made this flyer for a pancake brand and I’m really proud, clean layout, soft pastels, strong product focus. Kept it functional too with a referral offer, QR code, and location info. Client loved it and it’s going to print.