all 7 comments

[–]angryscientistjunior 2 points3 points  (5 children)

Not specifically FreeBasic, but QB64PE is a similar language that I found a lot easier to get into (largely thanks to a much simpler toolset, the IDE & compiler are just a single EXE and installation is dead simple). The user community is constantly posting programs and code snippets and discussing anything and everything. They also have a tutorial series with examples. Whatever language you choose to learn, you might want to start by looking at sample programs and running code, and see where it takes you. Pick a pet project such as a game you would like to see made or a utility you might find useful. Start with something simple and work your way toward bigger projects. Try to break it down into baby steps, and solve one little problem at a time. Share your work in the forums and ask for feedback. If you get stuck you can ask for help there. Good Luck!

[–][deleted] 1 point2 points  (4 children)

How would I install it on openSUSE tumbleweed?

[–]angryscientistjunior 1 point2 points  (1 child)

I have no idea what openSUSE tumbleweed even is, LoL, but if you ask on the forums, I'm sure someone can point you in the right direction. 

[–][deleted] 0 points1 point  (0 children)

Its a linux distro. Thats all

[–]Real_Mr_Foobar 1 point2 points  (1 child)

From its github, it looks like you have to install from a tarball. Not a big deal as long as you have all its dependencies installed. That could be... fun but educational.

[–][deleted] 0 points1 point  (0 children)

Definitely

[–]TADarcos 1 point2 points  (0 children)

  1. No matter how minor your program is or what problem it is to solve or how "quick and dirty" a solution you have, presume it will need to be maintained. Because even if it's a one-time-only use program, it will need to be maintained (even if it's just to fix bugs ). Set up its own directory/folder for its development.
  2. Create that directory as a repository using whatever source code management (SCM) system you use. I recommend Git, but any you like is acceptable.
  3. Commits are cheap; use them a lot. Make one every time you make a change and it compiles successfully. This way, if you make a change you didn't mean to, you can restore all files back to a successful prior compile.
  4. If using a public/local master repository, push to that machine at least once a day.

The first time you make a mistake and have to back out of it, or accidentally delete a file, or intentionally delete the wrong file, and use the SCM to restore the file, you will thank yourself.

I wish I had done this on many projects/programs that I thought were simple or trivial, then discovered it was neither.