DEV Community: Charles Otugeh

Go Web Dev: How Proactive Communication Saves "Ghost" Projects

Charles Otugeh — Fri, 15 May 2026 13:50:19 +0000

The Power of Collaboration
Collaboration is the ultimate hack to overcome your weaknesses as a programmer. No matter how much time you spend reading documentation or writing isolated code, nothing accelerates your growth faster than working with a team. In Go web development, where concurrency, architecture, and performance matter immensely, bouncing ideas off others is the fastest way to level up.However, team collaboration is not automatic. It requires constant maintenance.The Day the Team Went Silent We recently kicked off a new Go web development project. We held our very first stand-up meeting to align on the architecture, and initial API endpoints integration. The energy was high, and everyone seemed ready to build.By the following morning, the reality of remote work set in.The team channel was completely silent. There were no new pull requests, no commits to the main repository, and zero public activity from some members. It felt like a "ghost project."It is easy to assume the worst when a team goes silent. You might think people are stuck, procrastinating, or confused about the requirements. Instead of waiting around for things to fail, I decided to take action.The Short Ask That Changed Everything I reached out to the team chat with a casual, non-judgmental check-in:"Hey team! Let's do a quick sync. Can everyone drop a screenshot or a brief note on what you've been working on so far?"The response was instant. It turned out that my colleague had not been idle at all. They were working locally on a complex continuous integration and deployment pipeline. Within minutes of my message, they replied with an updated workflow file, pushed their active local branch to Gitea, and asked for feedback.
The Gitea Actions workflow my colleague pushed from his branch models.

My Biggest Takeaway Sometimes "inactivity" isn't a lack of work it is simply a lack of communication.Programmers often get trapped in their own heads, trying to perfect a feature or fix a bug before showing it to the world. A simple, proactive check-in breaks that friction. It instantly aligns the team, exposes great work early, and unblocks momentum before time is wasted.Don't wait for the next formal meeting. If your project feels quiet, be the one to spark the conversation.

Gemma 4

Charles Otugeh — Tue, 12 May 2026 13:17:54 +0000

This is a submission for the Gemma 4 Challenge: Write About Gemma 4

Google recently unveiled advance AI agent called Gemma 4. This a multimodal and can give information in several languages, hence it is called multilingual. Gemma 4 can process text, video audio and images across one 140 languages. In addition Gemma 4 exhibits high performing rate, optimizing intelligence. the following parameters are exhibited by Gemma 4: Mixture of Expert which is for strong reasoning this enable a strong functionality and complex performance and supporting AI root-use-protocol. Lastly, Gemma 4 can work multiple hardware.

Advantage of Gemma 4 for developers and industries

It offers Effective @B and $B available for device using edge and mobile.
26B offers higher efficiency while 31B for large-scale and sophisticated performance. Deployment for Gemma 4 depends on Ollama, llamacpp, vLLm and Unsloth.
NVIDIA and TPU
API which is accessed gemini Google AI Studio.

ASCII-Art Web

Charles Otugeh — Wed, 22 Apr 2026 15:23:06 +0000

Over the past two weeks, I have made great progress in Go. I implemented a small program that accepts user input and displays ASCII art on a webpage. What I learned from this project is that it can be embedded on the web to display blurred images.
The interesting part was implementing a mapping server to GET static files from the static directory:

fs := http.FileServer(http.Dir("static"))

This line handles the GET requests by mapping CSS to the Go backend. It is implemented at the top of main.go, followed by this line:

http.Handle("/static/", http.StripPrefix("/static/", fs))

I enjoy using HTML and CSS to create nice-looking webpages.

follow the link to get the whole code: https://github.com/ckotugeh/ascii-art-webs

Golang vs JavaScript

Charles Otugeh — Sat, 21 Mar 2026 16:08:34 +0000

Golang Experience in Comparison to JavaScript: A Practical Perspective
In the modern software landscape, developers often find themselves choosing between multiple programming languages depending on the problem they want to solve. Two popular choices Golang (Go) and JavaScript (JS) offer very different development experiences. While both are powerful in their own right, they differ significantly in philosophy, performance, ecosystem, and use cases. This article explores what it feels like to work with Golang compared to JavaScript from a practical, developer-focused perspective.

Language Philosophy and Design

Golang was designed with simplicity, performance, and concurrency in mind. Its syntax is minimalistic, avoiding unnecessary abstractions and enforcing a strict structure. The language encourages clarity over cleverness, making codebases easier to read and maintain.
JavaScript, on the other hand, is highly flexible and dynamic. Originally built for the browser, it has evolved into a multi-paradigm language supporting functional, object-oriented, and event-driven programming. This flexibility is powerful, but can also lead to inconsistency across projects.
Experience takeaway:
Go feels disciplined and predictable.
JavaScript feels expressive but sometimes chaotic.

Performance and Efficiency

Performance is one of Golang’s strongest advantages. Being a compiled language, Go produces fast, efficient binaries that run close to system-level performance. It is particularly well-suited for back-end systems, APIs, and microservices.
JavaScript, being interpreted (or JIT-compiled), is generally slower in raw execution. However, modern engines like V8 have significantly improved its speed. Still, for CPU-intensive tasks, it lags behind Go.
Experience takeaway:
Go excels in performance-critical applications.
JavaScript is “fast enough” for most web use cases.

Concurrency and Scalability

Concurrency in Go is a standout feature. With goroutines and channels, developers can easily write concurrent programs without dealing with complex thread management. This makes Go highly effective for scalable backend services.
JavaScript uses a single-threaded event loop with asynchronous patterns like callbacks, promises, and async/await. While powerful, handling concurrency can become complex, especially in large applications.
Experience takeaway:
Go makes concurrency simple and natural.
JavaScript requires more careful handling of async logic.

Tooling and Developer Experience

Golang comes with built-in tooling that works seamlessly; formatting, testing, dependency management, and compilation are all standardized. This reduces setup time and eliminates “tool fatigue.”
JavaScript has a vast ecosystem with countless tools, frameworks, and libraries. While this provides flexibility, it also leads to fragmentation. Developers often spend time choosing and configuring tools rather than building features.
Experience takeaway:
Go offers a smooth, consistent development workflow.
JavaScript offers choice—but at the cost of complexity.

Ecosystem and Use Cases

JavaScript dominates frontend development and is essential for building interactive web applications. With Node.js, it also powers backend systems, making it a full-stack language.
Golang is primarily used for backend services, cloud infrastructure, and DevOps tools. It shines in building APIs, distributed systems, and high-performance servers.
Experience takeaway:
JavaScript is unavoidable for web interfaces.
Go is ideal for backend performance and reliability.

Learning Curve

Golang is relatively easy to learn due to its small syntax and strict rules. Developers can become productive quickly.
JavaScript has a steeper learning curve—not because of syntax, but due to its quirks, asynchronous behavior, and evolving ecosystem.
Experience takeaway:
Go is beginner-friendly and straightforward.
JavaScript requires deeper understanding over time.

Conclusion

Choosing between Golang and JavaScript is less about which language is better and more about which is better suited to your needs.
If you want simplicity, performance, and strong concurrency Go is an excellent choice.
If you need flexibility, rich ecosystems, and frontend capabilities JavaScript is indispensable.
Many modern systems even use both: JavaScript for the frontend and Go for the backend. Understanding the strengths of each allows developers to build more efficient, scalable, and maintainable applications.
In the end, the best developers aren’t loyal to one language thLearning Curve
Golang is relatively easy to learn due to its small syntax and strict rules. Developers can become productive quickly.
JavaScript has a steeper learning curve not because of syntax, but due to its quirks, asynchronous behavior, and evolving ecosystem.
Experience takeaway
Go is beginner-friendly and straightforward.
JavaScript requires deeper understanding over time.They're fluent in choosing the right tool for the job.

By Charles Otugeh
Penetration tester,Software Developer apprentice at Zone01 Kisumu
kotugeh@gmail.com
+254704433824