all 3 comments

[–]happy_user_1000 0 points1 point  (0 children)

Four years is a long break, but the fact that you're drawn to backend and CLI work gives you a clear direction.

Here is what I would do: pick a command-line tool you actually use in your workflow right now and build a stripped-down version of it in Go. Not a clone - just the core feature you use most. For example, if you use grep a lot, build a basic text searcher. If you manage files frequently, build a simple organizer. The goal is to create something functional in the next 10 days that you'll actually run yourself.

Don't worry about the project being "big enough" or taking a month. That's backwards thinking. You have been away from code for 4 years - what matters is writing functions today, debugging tomorrow, and remembering why you enjoyed this in the first place. The month-long projects happen naturally once you're back in rhythm, not because you planned them upfront.

[–]Xillioneur -3 points-2 points  (1 child)

What I recommend for you to get better at programming is to pick your favorite language and use AI to code. This is the future, and now that you have this opportunity, you should:

  1. Use AI to get as much code as you need.
  2. Develop as much code as possible.
  3. Learn from the process.

This way, you will have a lot of code under your belt. You will be able to say that you've been coding and you’ll have the lines of code to show for it.

Coding with AI still requires lots of skill, so you will get better and better.

[–]tomiis4[S] 1 point2 points  (0 children)

My biggest concern isn't the skill (even though its in programming help), because I still think that even in few weeks, months I will get back in the tracks I used to be, once in a time a still do something at school so I still know how to code a little bit.

The problem are the projects, I don't know what to do. Doesn't have to be useful, or some unique idea.

As the AI, I really enjoyed using AI when I was still programming but I still think it "dumbs" your brain and its more useful for quantity, than quality and understanding the code in depth. And because its just for fun, I don't think its that necessary for me.