Ferdi

cuma iseng, sisanya beruntung
🇵🇸

[Ferdi @feerdim]

https://t.co/VOXUsMhenV

[Cygames ID @Cygamesid_en]

To celebrate #CygamesID linking services with #Umamusume: Pretty Derby, we're offering Trainers a chance to win 1,500 carats!

-Follow @Cygamesid_en
-Repost this post

Register your Cygames ID and get access to exclusive deals on the Cygames WebStore!

https://t.co/XijUO9vIHC

[Abhishek Singh @0xlelouch_]

Your Golang knowledge, explaining:

Goroutines
Channels
Context cancellation
WaitGroups
Mutex vs RWMutex
Buffered vs unbuffered channels
Worker pools
Select statements
Interfaces
Error wrapping
Generics
net/http internals
gRPC in Go
sync.Pool
io.Reader / io.Writer
Goroutine leaks
Escape analysis
Zero-allocation patterns
Race detector
Memory profiling with pprof

Interview decision:
Sorry, we need someone who actually knows when to use a goroutine.

Knowing Go features ≠ knowing Go engineering.

I’ve seen engineers spin up 100 goroutines for a task that should’ve been a simple for-loop.

They knew what a goroutine is.
They didn’t know why to spawn one.

Understanding fundamentals in Go means asking better questions:

---

1. Do you really need concurrency here?

Just because Go makes concurrency easy doesn't mean everything should be parallelized.

If your job is CPU-bound
— concurrency won’t give you a speedup.

If your job is I/O-light
— concurrency might hurt performance.

Many Go beginners accidentally create spinning goroutine storms for trivial tasks.

---

2. Should this be a goroutine or a worker pool?

Goroutines are cheap — not free.

Thousands? Fine.
Millions? You’ll crash your service.

Worker pools add backpressure, limit concurrency, and prevent cascading failures.

Correct concurrency is about control, not enthusiasm.

---

3. Is a channel even the right abstraction?

Channels are not the default.

Sometimes:

a simple slice is faster
a mutex is simpler
a pipeline is unnecessary
atomic values give lower overhead

Channels introduce synchronization.
Synchronization introduces latency.

Engineers who love channels often write code that’s “clever” instead of correct.

---

4. How will this context propagate?

Most Go outages happen because developers:

forget to cancel contexts
pass background context everywhere
leak goroutines waiting on dead channels
ignore deadlines

If your system doesn’t handle cancellation properly, you don’t have a Go service — you have a time bomb tbh.

---

5. Have you run the race detector, profiler, and escape analyzer?

If you write Go without:

go test -race
go tool pprof
go build -gcflags="-m"

…then you're guessing, not engineering.

Being able to explain:

why a value escapes to the heap
why CPU usage spiked
why memory is ballooning
why goroutines aren’t releasing
is what separates a “Go tutorial graduate” from a real Go engineer.

---

6. Does this service need Go?

Go shines in:

high-throughput APIs
distributed systems
infrastructure tools
networking services
event processing
real-time pipelines

Sometimes Python is better.
Sometimes Rust is better.
Sometimes PostgreSQL stored procedures outperform your Go service entirely.

Knowing Go means knowing when not to use Go.

---

The best Go engineers aren’t the ones who know every feature.

They're the ones who can explain:

why this should NOT be concurrent
why this needs a mutex, not a channel
why this code must avoid allocations
why this API should return errors, not panics

why a simple goroutine is not a “system design pattern”

Anyone can memorize go routines + channels = concurrency.

Not everyone can architect a system that runs clean for months without leaking memory, burning CPU, or failing under load.

That’s the difference between Go as a language and Go as an engineering discipline.

[Ferdi @feerdim]

I just published GOLANG INTRODUCTION https://t.co/m5xj38Due1

[Ferdi @feerdim]

I just published DATABASE ACID TRANSACTIONS https://t.co/Y427X7wO28

[Ferdi @feerdim]

I just published DATABASE FUNDAMENTALS https://t.co/N7ogFpTrhp

[Fathan @veefathan]

@hrdbacot

[Ferdi @feerdim]

@fleurishana di depan!

[Ferdi @feerdim]

@fifiyuu GOOO

[Ferdi @feerdim]

https://t.co/wZjCe8FACw

apa lagi ini

[Ferdi @feerdim]

@cinnamo0ns_ @farrellmattthew kalo tailwind udah pasti mobile first

[Ferdi @feerdim]

@tekotokofficial

https://t.co/ETnyuSYGWe

[Imre Nagi @imrenagi]

@clavinjune Gorm ini kayak narkoba. Bikin bodoh 🤣

[Ferdi @feerdim]

🥲
https://t.co/8lMyLylxyg

[Ferdi @feerdim]

kaya kenal soundtrack nya https://t.co/4mdRoAU8yA

[【OSHI NO KO】Global @oshinoko_global]

🌟【SEPTEBER 2023 GIVEAWAY】🌟

Thank you for supporting【OSHI NO KO】!

In celebration for fans outside of Japan, here is the second monthly giveaway.

💫 RETWEET & FOLLOW to enter for a chance to win a a photo card signed by Yurie Igoma (VA of Ruby)! #oshinoko_giveaway

[fleurishana 🌻 @fleurishana]

「 アイドル」 / IDOL -versi Indonesia- (tv size)

➤ Vokal: fleurishana
➤ Lirik Indonesia: @myrrr_myrrr | https://t.co/6x4tZkpF90
➤ Penyelaras (Sound Engineer): @Timun_kun69 | https://t.co/kX7GnXz3sH

Dukung aku di https://t.co/cB9IeyfXLX 🌻

[Ferdi @feerdim]

@Elfar9998 @diiiiky wew gua sampe baca komiknya

[Ferdi @feerdim]

https://t.co/T6arPkKRJY

[Ferdi @feerdim]

@drocketxoxo @caritemenajakok @codingfess di settings ke bagian billing and plans, disitu enable github copilotnya