Skip to content
View jR4dh3y's full-sized avatar
👾
Fighting with clanker slop
👾
Fighting with clanker slop

Highlights

  • Pro

Organizations

@i-got-this-faa @gdgoc-miet

Block or report jR4dh3y

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
jR4dh3y/README.md

The Definitive Guide to Becoming a Programmer

Learn to code. Coding's dead. Learn AI. Don't use AI. You'll never learn the fundamentals. Learn the fundamentals. Nobody writes Assembly. Learn C, it makes you a better programmer. Nobody writes C. Use Copilot, everybody does. Don't use Copilot, they can tell. Use Cursor. Cursor's making you worse. Vibe code an app. Vibe-coded slop doesn't scale. Ship fast, don't ship slop. Let AI write the boilerplate. Don't let AI write anything you can't debug. Read what it generated. If you're reading it that carefully, write it yourself.

Learn prompt engineering. Prompt engineering isn't a job. Learn machine learning. Everybody's learning machine learning. Do what nobody's doing. But do what's hiring. Use a framework. Frameworks make you lazy. Learn React. React is bloated. Learn Rust. Nobody's hiring Rust. Learn Go. Learn Python. Python's too slow.

Learn TypeScript. Just learn JavaScript properly. Pick a stack. Don't be pigeonholed. Specialize. Be full stack. Be T-shaped. Depth beats breadth. Breadth is leverage. Write tests. But tests slow you down, so move fast and break things. But don't break prod. Comment your code. But good code doesn't need comments. Read the docs. But the docs are wrong. Read the source. You don't have time to read the source.

Ask for help. Don't ask what you could Google. Just Google it. But don't just Google it, understand it. Learn Git properly. Just memorize four commands. Learn Docker. Learn Kubernetes. You don't need Kubernetes. Learn the cloud. Cloud costs will bankrupt you.

Build side projects, but not another to-do app. Build something original, but don't reinvent the wheel. Solve a real problem. Scratch your own itch. Nobody wants your itch. Finish your products. Ship at eighty percent. Ship at forty. Don't launch broken. Get users. Talk to users. But users don't even know what they want. Build what you'd use. But you're not the market.

Green your GitHub. Nobody looks at your GitHub. Contribute to open source. Your PR has been open for eight months. Fix a typo in the docs. That counts. That doesn't count.

So anyway, just build shit.

My oss contributions

Pinned Loading

  1. BoxBox BoxBox Public

    A modern, self-hosted web based file manager for your homelab. Built in SvelteKit & Go

    Go 320 8

  2. i-got-this-faa/fbs-core i-got-this-faa/fbs-core Public

    Fast Blob Storage (FBS) is a s3 compatible blob storage and CDN solution primarly for self hosting

    Go 52 1

  3. HPOmen-linux HPOmen-linux Public

    A Linux-first control surface for HP Victus and Omen hardware written in Vala. Features a Fan and Power Controls

    Vala 7

  4. rsclip rsclip Public

    Wayland clipboard manager with a Rust daemon, GTK4 overlay UI

    Rust 6 1

  5. dots-niri dots-niri Public

    dotfiles for niri window manager

    Shell 33 2

  6. nonchalant-shell nonchalant-shell Public

    Niri-first Wayland desktop shell built with Quickshell

    QML 6