Building devdevbuilds: combining backend projects, cybersecurity learning, and design assets
I’m starting to use DEV Community as a place to document what I’m building, what I’m learning, and how my projects are developing over time.
Right now, I’m building devdevbuilds, a freelance-focused development and design brand. The goal is to create a small but polished brand around practical development work, clean technical visuals, landing pages, backend projects, dashboards, and portfolio-ready assets.
What I’m focused on
My current focus is split across a few connected areas:
- Backend development
- Cybersecurity fundamentals
- API design
- Technical documentation
- Project dashboards
- Landing pages
- Brand kit and visual asset design
That mix may seem broad, but it all connects to the same idea: building useful digital projects that are clean, understandable, and presentable.
Current pinned projects
I pinned ZeroSOC and Geofence because they represent the technical side of what I’m trying to grow.
ZeroSOC is my cybersecurity/backend portfolio project. It is focused on local monitoring, API structure, security events, logs, metrics, and dashboard-style visibility.
Geofence represents a different kind of technical thinking: location-based logic, spatial concepts, and product-style problem solving.
Together, they show the direction I’m aiming for: practical builds that combine backend logic, security-minded development, and clean presentation.
Why devdevbuilds?
I’m building devdevbuilds as a working identity for freelance development and design work. It gives me a place to organize client-ready assets, project documentation, brand visuals, and technical builds under one name.
The brand is still in active development, but that is part of the point. I want to document the process instead of only showing finished work after everything is polished.
What I’m learning right now
I’m currently working through cybersecurity training, backend development practice, GitHub workflows, project documentation, and better ways to present technical work clearly.
A big part of this process is learning how to move from “I built something that works” to “I built something that someone else can understand, review, and trust.”
That second part matters. A working project is good. A working project with clear documentation, screenshots, structure, and purpose is much stronger.
What I’m hoping to share here
I plan to use DEV to post about:
- Backend project progress
- Cybersecurity learning notes
- API and dashboard builds
- Portfolio project cleanup
- Branding and design assets for technical projects
- Lessons learned while building devdevbuilds
I’m also interested in feedback from developers, designers, cybersecurity learners, and anyone building portfolio projects from scratch.
Feedback welcome
If you have advice on building a stronger developer portfolio, improving project presentation, writing better technical documentation, or balancing development and design work, I’m open to it.
This is the starting point. More builds, notes, and project breakdowns coming soon.
