Chinweike (@Chinwe_script) profile picture

HNG12 & HNG13 Finalist | Software Engineer | AI Enthusiast | Exploring Go https://nitter.cf/t.co/NiaAA5YESY

Lagos, Nigeria
Joined March 2023
Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)Photo by Chinweike (@Chinwe_script)
#Hello, I’m Chinweike. A Full-Stack Developer (Web2 × Web3). If it can be built, I’ll figure it out. All I need is time and studies. Currently open to work: freelance, full-time, or contract. Let’s build something amazing!
1
7
371
A Nigerian lady shares how moving to Ukraine for study to becoming a refugee due to an active war. 🏷️ IG/the_oluwaseyi_
209
1,160
203
7,553
3,900,004
Do you remember when you joined X? I do! #MyXAnniversary
9
Chinweike retweeted
Full stack in tutorials, real stack in the job.
13
9
1
128
3,398
No announcement, just receipts. More commits to commit. Happy new month.
1
18
Building with Go - Day 30 - Integrated Gemini AI into scanr via a unified reviewer interface - Added retries, quota-aware errors, and structured logging - Fixed a nasty goroutine sync bug blocking worker pipelines #BuildInPublic #GoLang
Building with Go - Day 29 - Built the AI reviewer abstraction layer for scanr - Added pluggable AI providers, unified config validation, and usage tracking - Turn mock reviews into real, provider-agnostic AI-powered code analysis #BuildInPublic #GoLang
2
1
68
Building with Go - Day 29 - Built the AI reviewer abstraction layer for scanr - Added pluggable AI providers, unified config validation, and usage tracking - Turn mock reviews into real, provider-agnostic AI-powered code analysis #BuildInPublic #GoLang
Building with Go - Day 28 Built a pluggable formatter system for scanr’s output layer Added JSON + JSONL formatters, a FormatterFactory, and exit code mapping for CI Turns structured scan results into machine-readable and automation-friendly output #BuildInPublic #GoLang
1
1
3
148
Building with Go - Day 28 Built a pluggable formatter system for scanr’s output layer Added JSON + JSONL formatters, a FormatterFactory, and exit code mapping for CI Turns structured scan results into machine-readable and automation-friendly output #BuildInPublic #GoLang
Building with Go-Day 27 Built a formatter abstraction for scanr’s output pipeline Added a TextFormatter with ANSI severity badges,a pluggable Formatter interface, and deterministic tests for CI Turns structured results into output humans can actually read #BuildInPublic #GoLang
1
111
Yes. Coding ≠ SE. It’s just a fraction of it. AI can be better at programming, but not at being a SE. The core of SE is problem-solving: systems thinking, trade-offs, architecture, constraints etc. AI didn’t take over SE. It removed the excuses and shifted the complexity.
This quoted post is unavailable.
2
17
Building with Go-Day 27 Built a formatter abstraction for scanr’s output pipeline Added a TextFormatter with ANSI severity badges,a pluggable Formatter interface, and deterministic tests for CI Turns structured results into output humans can actually read #BuildInPublic #GoLang
Building with Go - Day 26 Tests broke my worker pool. Wrote real concurrency tests, chased “send on closed channel” panics, fixed shutdowns and race conditions. Once tests passed, the system was solid. Tests didn’t just verify code. They fixed it. #BuildInPublic #GoLang
1
1
1
72
Building with Go - Day 26 Tests broke my worker pool. Wrote real concurrency tests, chased “send on closed channel” panics, fixed shutdowns and race conditions. Once tests passed, the system was solid. Tests didn’t just verify code. They fixed it. #BuildInPublic #GoLang
Building with Go – Day 25 Stabilized scanr’s review command. Refactored the review flow, cleaned up the worker pool, improved memory usage, and added solid concurrency tests for backpressure, retries, and shutdown. #BuildInPublic #Go
1
1
2
89
Building with Go – Day 25 Stabilized scanr’s review command. Refactored the review flow, cleaned up the worker pool, improved memory usage, and added solid concurrency tests for backpressure, retries, and shutdown. #BuildInPublic #Go
Building with Go – Day 24 Implemented scanr’s review pipeline: bounded worker pool, retries via a dead-letter queue, context-based timeouts, batch task submission, and basic metrics. Focused on controlled concurrency and predictable failure handling. #BuildingInPublic #Go
1
1
71
Building with Go – Day 24 Implemented scanr’s review pipeline: bounded worker pool, retries via a dead-letter queue, context-based timeouts, batch task submission, and basic metrics. Focused on controlled concurrency and predictable failure handling. #BuildingInPublic #Go
Building with Go – Day 23 Added a Dead Letter Queue to scanr to capture failed review tasks (errors, timestamps, retries) instead of losing them silently. Better observability, safer concurrency. #BuildInPublic #Backend #Concurrency
1
1
52
Building with Go – Day 23 Added a Dead Letter Queue to scanr to capture failed review tasks (errors, timestamps, retries) instead of losing them silently. Better observability, safer concurrency. #BuildInPublic #Backend #Concurrency
Building with Go - Day 22 Implemented a bounded concurrent worker pool for scanr to process code reviews in parallel. Controlled goroutine lifecycles, task queues, timeouts, retries, graceful shutdown, and pool metrics. #BuildingInPublic #Go
1
1
1
79
Don’t skip this. I really need a clear answer to this. Is having knowledge of Frontend + Backend the same as being Full-stack? Who really is a Full-stack Engineer?
24
Building with Go - Day 22 Implemented a bounded concurrent worker pool for scanr to process code reviews in parallel. Controlled goroutine lifecycles, task queues, timeouts, retries, graceful shutdown, and pool metrics. #BuildingInPublic #Go
Building with Go - Day 21 Focused on correctness and shaping the review system in scanr Added thorough filesystem tests, covered edge cases in file discovery, and started the review pipeline by defining core domain types like Issue for structured findings #BuildingInPublic #Go
1
1
71
Building with Go - Day 21 Focused on correctness and shaping the review system in scanr Added thorough filesystem tests, covered edge cases in file discovery, and started the review pipeline by defining core domain types like Issue for structured findings #BuildingInPublic #Go
Building with Go - Day 20 Integrated scanr with Git so it understands what actually changed, not just what files exist. Added repo detection, staged vs unstaged awareness, diff extraction, revision file reads, and fallback to full scans outside Git. #BuildingInPublic #Go
1
2
78
Building with Go - Day 20 Integrated scanr with Git so it understands what actually changed, not just what files exist. Added repo detection, staged vs unstaged awareness, diff extraction, revision file reads, and fallback to full scans outside Git. #BuildingInPublic #Go
Building with Go – Day 19 Worked on filesystem scanning for scanr, handling directory traversal, file filtering, and edge cases to keep behavior deterministic and testable. File discovery first, analysis later. #BuildingInPublic #Go
1
2
111
Building with Go – Day 19 Worked on filesystem scanning for scanr, handling directory traversal, file filtering, and edge cases to keep behavior deterministic and testable. File discovery first, analysis later. #BuildingInPublic #Go
Building with Go – Day 18 Started building scanr, a Unix-style CLI for structured code inspection. Today was about the CLI contract clear commands and flags, deterministic exit codes, input validation, and testable behavior. #BuildingInPublic #Go
1
1
103
In a backend interview you're asked: What happens when a user submits a request to a backend API? Answer⬇️
17