[ / / / / / / / / / / / / / ] [ dir / agatha2 / b2 / choroy / dempart / fanfic / jenny / kemono / throat ]

/tech/ - Technology

Winner of the 77nd Attention-Hungry Games
/x/ - Paranormal Phenomena and The RCP Authority

April 2019 - 8chan Transparency Report
Comment *
Verification *
Password (Randomized for file and post deletion; you may also set your own.)
* = required field[▶ Show post options & limits]
Confused? See the FAQ.
Show oekaki applet
(replaces files and can be used instead)

Allowed file types:jpg, jpeg, gif, png, webm, mp4, pdf
Max filesize is 16 MB.
Max image dimensions are 15000 x 15000.
You may upload 3 per post.

File: 93166db5f517961⋯.png (1.72 MB, 1280x1647, 1280:1647, Kagamihara_nadeshiko_Readi….png)


Hi /tech/, Well the thing is that i know the basics about programming (Variables, Booleans, Strings, Integers, Floats Conditionals, Loops, Functions, Classes, Inheritance, Polymorfysm) and i want to know... what's next? I feel lost right know cause i dont know what to do.

Should i get a job or what? Can you guys told me what's next once you learns the basics?


What's next is you build some things that are 100-1000 lines long. After that you read a book with the word 'intermediate" in the title


Whatever you do, don't sink into the language autism so common on this board.


>Classes, Inheritance, Polymorfysm [sic]

I wouldn't consider these basics. There are things that are way more important for programming.

Anyway, to learn more and get better at programming there's only practice. You have to write code on your own to figure out how to solve certain programming problems. Ideally you write programs that actually solve a problem you're interested in, such that the program is actually useful in the end. However you can also look at other example programs if you're out of ideas. Also, if you have found an interesting idea for a program but you decide not to write it because you think it's too difficult or you don't know how it's going to work, try writing it anyway. Those are great opportunities to learn something new.

The important part is that you focus on what actually matters (i.e. writing programs). You need to write code daily and without anyone else holding your hand. It's not easy, but that's the only way to get the necessary practice to get better at it.



Codecademy's Python training would be good, then followed by its web development course (+ Vue if you want more diversity).


Unfortunately it really depends on what you want to do.


Go ahead and learn all the Javascript necessary *or pull in 500MB of "libraries" to make your art project webpage that occupies 3 GB of RAM.


C. Learn about how high level programming concepts don't apply all the way down. Get used to pointers. Algorithms (sorting, hashing, prng, etc), data structures; some stuff about the OS, CPU, memory so you can optimize your program. Cry about buffer overflows and use after frees or something and get stuck in an endless loop of debugging and optimization.


If you want to just like make game, stick to an engine or at least a library, or you'll end up like certain people on /agdg/.

>other domains

No fucking clue; never done those.

But the other posters are right. There's a massive difference between thinking you know the basics and actually being able to write a program to solve a real problem, rather than a textbook problem.



>If you want to just like make game, stick to an engine or at least a library, or you'll end up like certain people on /agdg/.

Okay, I have some experience with that so let me say - yes, use an engine. I was really anti-engine for so long but there are really no good libraries below that level. Allegro5 is the best, which really means "yeah I suppose I can deal with this crap".



The more general purpose built (for 3d games) engines like Godot, Unity, Unreal Engine are kind of shit, for multiple reasons. You're better off learning some graphics programming and studying id tech's engines



I uaed sfml for a while seems pretty good and free and multiplatform. You just havr to code some shit yourself a engine would usally do yourself


read gentoo and install sicp




>/v/ encourages learning to make your own game engine while /tech/ tells you to use Unity

The absolute state of this fucking board



What did you mean by this?




Unity is botnet



Makes me fucking weep.



>/tech/ is full of LARPers

>/agdg/ less so



File: 430640b11b9fd85⋯.png (121.8 KB, 2748x1716, 229:143, anagramfinder.PNG)


Can you understand what's going on in the class, yuru camper? The for-loops don't need to be nested, and it struggles with duplicate, non-whitespace characters in the same string.



when was the last time /v/ finished a game?



This isn't even a complete list because nobody cares about the wiki http://8agdg.wikidot.com/general:finishedprojects

When was the last time /tech/ finished a videogame-size project?



>When was the last time /tech/ finished a videogame-size project?

When was the last time /tech/ finished a project at all?


for the love of god whatever you do just dont use unity



When was the last time /tech/ finished a project?



Hey that LISPfag made a non-working text editor in a mere six months!


File: c6c8e177bd86ef2⋯.jpg (7.63 KB, 132x209, 12:19, foto.JPG)



>>When was the last time /tech/ finished a videogame-size project?

>When was the last time /tech/ finished a project at all?

When was the last time /tech/ started a project (and got beyond creating a logo)?



Meanwhile all the Cniles on here haven't.


File: 8c82f2686107c74⋯.jpg (14.03 KB, 220x318, 110:159, SICP_cover.jpg)


Just start hacking. It would also be best if you read this book (http://web.mit.edu/alexmv/6.037/sicp.pdf). Just because you know how for-loops work and you can make strings, functions, (((classes))), etc. doesn't mean you've mastered hacking.



man vim



Read through the security portion in the back of the book. Make sure your programs are locked down. Do an intermediate tutorial series in your given language on YouTube or something like that. Find ebooks or turtorials on network progamming, AI, game programming, or learn to create really cool GUIs. If you make Linux GUIs people will appreciate it.

Learn how to hack, then pentest your own applications. Write some hack tools. A hash cracking programming is an easy start and it has a legitimate purpose. Pure brute force with nested loops or a dictionary attack with read through a file line by line and try the hashing algorithm against each string and compare to string output the corresponding plaintext if the hashes match. Pretty simple.

Web authentication with curl.

Port scanners can be kinda fun. You can go really simple or you can put a lot of bells and whistles into it. Try to make a program that will find a specific service like image board sites, or check if site is given server is running http/https common ports 80 8080 8000 443 etc then parse the html for a given string like 'Tinyboard Copyright © 2010-2014 Tinyboard Development Group' or something like that.

Find a piece of software that is a pain in the ass to install and write a script for it.

Like if a C++ program has an #include statement that has the wrong library path write a program that will read through the includes and use a program like whereis to return the correct library path and check if the it's right in the source code and if not change it to the correct path before compiling.

Write an install script for various cryptocurrency wallets and miners.

Write an application that will turn your plaintext or rich text into HTML pages.

Then write a program that will generate a site map of your pages.

Write a web spider.

Write a chat bot.

Write a command shell or a RAT.

Write a program that automates a bunch of command line programs. Say a process take like 50 or so commands in CLI to handle write a program or script that will do it with a command and maybe some arguments.

Write a picture board.

Write a chat server and client.

Just a few ideas off the top of my head.



Gotta love Java.



Using an engine godot is the objectively correct way to make a game.

Making your own engine is the objectively correct way to improve your programming skills.

Two different goals.



Sure buddy, show me all the hot games that were made with Godot.

Hard mode: without copypasting some obscure flash game-tier shit from Godot's website.

Godot is a piece of shit, the only reason it's relevant at all is because it's the only unity-style FOSS game engine.




You use a game engine because it takes care of a significant portion of game programming problems allowing the programmer to focus on the game and not reimplementing universal game problems.



>universal game problems

There's universal problems but no universal solutions past the point of creating a window. Using an engine is the "objectively correct" way to make a game in the same way that using Electron is the objectively correct way to make desktop applications. Just because it's easier doesn't mean it's better, in fact "easy to use" and "good result" are usually opposing forces.



You may have your points but when it comes to creating highly detailed 3d game worlds you usually have very similar problems and solutions.

>in fact "easy to use" and "good result" are usually opposing forces.

Depends on available work force. Only very big studios or very skilled developers can afford an own engine without the game suffering from the engine being a piece of shit.


>Sure buddy, show me all the hot games that were made with Godot.

I remember >>>/agdg/ making some sweet looking things with Godot.


I like löve, nice 2D game framework and lua is a fun scripting language that lets you both churn out code quickly and is also fast enough itself to do some pretty complicated shit without being slow as molasses like python or java. You can also trivially bind in external C libraries either with your own code or code of others. Underrated language and underrated framework. I think it's not used often because even though it's lua, you have to kind of know how to do things and can't just click together something like with unity.



File: 0353e004c6ad93d⋯.png (121.51 KB, 1904x1589, 272:227, cuteprogram.PNG)



This is how any programmer in any language will perform when they don't understand how to use the standard library.


File: 4b42781b6b58a82⋯.png (956.5 KB, 1892x966, 946:483, ClipboardImage.png)

pretty based



oops wrong thread lol, sorry

[Return][Go to top][Catalog][Nerve Center][Cancer][Post a Reply]
Delete Post [ ]
[ / / / / / / / / / / / / / ] [ dir / agatha2 / b2 / choroy / dempart / fanfic / jenny / kemono / throat ]