---
title: "Discussion on \"Building The Go Engineer: Teaching Go as a Software Engineering Discipline\" | Hashnode"
description: "Discussion on \"Building The Go Engineer: Teaching Go as a Software Engineering Discipline\". Why I designed The Go Engineer as a repository-first, release-quality curriculum for learning production-shaped Go."
url: "https://hashnode.com/posts/building-the-go-engineer-teaching-go-as-a-software-engineering-discipline/69fb2f8750ecad45331fa021"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building The Go Engineer: Teaching Go as a Software Engineering Discipline](https://the-go-engineer.hashnode.dev/building-the-go-engineer-teaching-go-as-a-software-engineering-discipline?utm_source=hashnode&utm_medium=feed)

Why I designed The Go Engineer as a repository-first, release-quality curriculum for learning production-shaped Go.

May 6 · 17 min read · the-go-engineer.hashnode.dev  
Read the article

-   [#go](https://hashnode.com/tag/go)
-   [#golang](https://hashnode.com/tag/golang)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#backend](https://hashnode.com/tag/backend)
-   [#architecture](https://hashnode.com/tag/architecture)

## Written by

[RASEL HOSSEN](https://hashnode.com/@rasel9t6)

@rasel9t6

  
[View profile](https://hashnode.com/@rasel9t6)

## Responses 2

Markdown supported · ⌘↵ to post

[Marcelloh](https://hashnode.com/@marcelloh)

[May 7](https://hashnode.com/posts/building-the-go-engineer-teaching-go-as-a-software-engineering-discipline/69fb2f8750ecad45331fa021/comment/69fc310d3d9a9c10196d12ad)

It is an interesting read. If I have time, I will look at the code.

[RASEL HOSSEN](https://hashnode.com/@rasel9t6)

[May 7](https://hashnode.com/posts/building-the-go-engineer-teaching-go-as-a-software-engineering-discipline/69fb2f8750ecad45331fa021/comment/69fc310d3d9a9c10196d12ad#reply-69fc32563d9a9c10196e48b0)

Thank you, [Marcelloh](https://hashnode.com/@marcelloh "Marcelloh") — I really appreciate that. If you get time to look at the code, I’d be grateful for any feedback, especially around Opslane, project structure, and production Go topics.
