LinkedIn Has Great Advice

A surge of Go + React full-stack boot camps is being treated as a signal that Go is moving from “backend niche” toward mainstream professional use—especially for building web servers—while hiring managers may soon expect candidates to know Go’s core language mechanics, not just surface-level frameworks.

The discussion starts with a LinkedIn-style post claiming that more Go-focused training is appearing online, and the reaction is broadly positive: Go is described as a web-server-oriented language, which makes it “nice to write web servers” and, in turn, attracts more developers who want a practical, purpose-built tool. Go’s rise is framed against Java’s long dominance in backend web work, with the comparison emphasizing timing: Java’s ecosystem took off earlier (and later co-evolved with JavaScript), while Go arrived later (around 2011) but is already showing “serious waves.”

That momentum is paired with a warning about interview filtering. As new markets form, many newcomers will enter—often without deep understanding—so employers may increasingly reject applicants who can’t answer foundational Go questions. Specific gaps called out include not knowing pointers, not understanding how slices and maps work under the hood, and not following Go’s idiomatic interface patterns (the “receive interfaces, return structs/strings” style is mentioned as a common expectation). The tone is less about gatekeeping for its own sake and more about aligning hiring expectations with what Go developers should be able to reason about.

The transcript then pivots into technical nitty-gritty. Slices are described as potentially “dangerous” because they can be mutated in ways that affect underlying memory, especially when slices are created as offsets into arrays. Maps are treated as another area where interview questions can expose shallow knowledge: the explanation sketches hashing into a bounded memory region, storing key/value pairs, and using collision-handling strategies (with references to linear vs exponential backoff as a way of thinking about probing). The discussion also contrasts arrays/lists versus sets, arguing that contiguous memory and fast integer comparisons can make arrays competitive for small sizes, while sets become preferable as item counts grow.

Beyond Go, the conversation challenges the idea that developers should “choose one techfield and stay with it.” Familiarity across areas is defended as more fun and more useful, as long as someone also develops depth. Front-end specialization is criticized when it becomes shallow—examples include overemphasizing npm without understanding underlying data structures, or treating HTML as only divs without accessibility considerations.

Finally, the transcript broadens into career strategy: learning stricter languages (examples mentioned include Odin, Zig, Rust, and C) is presented as a way to strengthen computer science fundamentals and improve how people write code in other stacks. Rust is positioned as distinct from “low-level” expectations because many Rust developers rely on patterns like Arc/Mutex and don’t focus on memory layout directly, whereas Zig is described as more likely to force explicit thinking about memory layout. The segment ends with advice about LinkedIn itself—LinkedIn can help with jobs (a Netflix example is cited), but LinkedIn influencer content should be treated cautiously, and the best first post is framed as choosing a language/topic that can be communicated to the widest audience (with JavaScript as the baseline).