Step 1: Google
Step 2: Copy
Step 3: Paste
Step 4: Go to Step 1
Post funny things about programming here! (Or just rant about your favourite programming language.)
Step 1: Google
Step 2: Copy
Step 3: Paste
Step 4: Go to Step 1
More like :
This is fucking dumb. People learning how to code don't know how to start. They don't know what to start writing or where to start on it. This is akin to telling a depressed person "just don't be sad".
Exactly. If you know nothing about a topic, you don't even know, what exactly to google, except "how to make computer do stuff".
The initial hurdle of incompetence can be extremely frustrating and almost impossible to climb, if you don't have guidance.
"I would contribute a PR but I don't know Go!"
Alright, I learned graduated harvard and learned how to code, now how do I center a div?
Source: the actual harvard university website
Starts typing gibberish in Microsoft Word because the magic hand still hasn't told me how to get started coding.
Alright, smart guys. I know how to code. How do I make these variables into a an app?
Honestly I've been trying to learn coding for a while, and there's a huge chasm between knowing a language and doing something with it that I can't go over. I want to make an app to create ttrpg character sheets... Alright how do I make my code into something with an UI? How do I turn it into an executable? How do I turn these lines into SOMETHING?
What OS do you run? Are you planning on sharing this app with others? Should it be a web app?
Happy to help!
As stupid as it sounds, you build small blocks and put them together.
In your case, build a console app, that (for example) creates basic sheets. Then you build a small text only interface to plug actual values into the file, then you can think about a GUI.
Many beginners (myself included) want to go from 1 to 100 immediately, but that's almost impossible. You tackle small problems first and then step by step go further.
You may have heard of startups building MVPs, minimum viable products. The basic core of what functionality you want to have. That's where you start.
this is where branches of coding splitoff, as learning the fundamentals of coding doesn't stop there, its a field where you have to pick up new skills on the go because not everyone needs it.
some people never touch apps because they might work backend or engineering, some people might not touh databases because they arent the ones dealing with CSV files. some people never touch web development (because its not engineering in some jurisdictions /s)
If i have to make a crude comparison, think of it like driving. basic driving knowlege is knowing how to drive a car. Knowing how to drive a car doesnt imply they know how to drive a boat, formula vehicle, big truck, forklift and such, so you need to go into further training for those, but you never should expect someone to cover all usecases.
Then what's the class C passenger vehicle license of coding that everyone needs to survive in the modern world from teenagers to grandparents? I just want to drive a sedan from point A to point B, maybe pick up a piece of furniture from Costco or a litter from soccer practice in an SUV once in a while.
the basics of coding is less the language, but more the algorithms and pracices.
knowing concepts like object oriented programming is language agnostic. how you learn OOP can be done with several languages, usually most commonly with Java or Python, but it fundamentally doesnt matter for the common languages for the most part.
Assembly
This has always been my issue with programming. I can visualize how to build a chair, I know what I need to build it and I know what it needs to do. I know how screws work, and I understand when glue is applied.
But with programming it's like i know what the word wood is and I know what the word fabric is, but I haven't the slightest idea how I use any of it to make anything useful. I can't even start to build a plan because I don't even know what's needed for any specific thing.
At least you have an example of what you want to make, I don't even know what I want to make so it makes "figure it out" even harder lol
There's pretty much only two ways you can go about it in my experience:
Fail forwards and try cobbling something together, constantly using search engines to fix errors or finding libraries or getting help with those libraries. One thing you'd have to figure out is an order of operations - what do you code and in what order, which might be tough for someone new but I'd say it's well worth it.
Find some tutorial to a project and try following it (those that have step by step guide on what you should do without letting you copy paste code), then using the knowledge you gain to do the way #1 above to hopefully have an easier time figuring out the order of operations, plan out your program and what you're gonna be coding.
Don't think you can avoid getting hands-on and coding something up by yourself. General coding tutorials can only get you so far and are often harmful if abused too much (aka being stuck in tutorial hell).
That is a really good point, and there isn't a one answer first all. If you're looking for a mobile app, then you could do Android studio or Swift for IOS. If you only want to develop one app for both, then maybe you should just do an electron app that is essentially just a website.
These tools will either have a visual interface editor, markdown language (like html), or a way to define visual components in code. After programming an app you can build, which will give you the appropriate executables for the different platforms.
If you're looking to start simple, then use something like pygame to learn the basics of using a visual interface.
If this is not a meme...
You know how you have to look up... errors when you don't know what they mean?
That.
Figuring out how to do something specific, like UI, works just like that. All the time. It's "looking up how it works", then "messing around with it until it does" all the way down.
If you are just starting out, coding something in HTML and javascript might be intuitive, because you can see and run it right away. Otherwise you will have to figure out how to use some kind of UI framework in the language you're using. Because they're all different. Yeeeaaah...
I think it's harder for compiled languages and easier for interpreted ones.
Look for some UI libraries. They provide functions and classes that you can call that will draw things to the screen. As for the executable part that varies per Language. If you want help dm me and maybe we can do a discord call!
I never noticed before, but it looks like DeForest Kelley is struggling to keep a straight face in that scene..
Keyboard for coding, mouse for games.
Wtf, don't tell the plebs how it works!! They're going to figure out how easy it is!
I'm not sure I get it. Is there a significance to him holding the mouse in front of him like that, instead of having it on the table like normal people? It seems to me that if you want to learn to code you should have your hands on the keyboard more.
The comic was originally about how to draw.
As people said, for coding you want to put his hands on the keyboard, not the mouse.
Draw... with a mouse??? Now I'm possibly more confused.
No he was holding a pen. Now he’s holding a mouse
No, on screen keyboard only!
If anyone genuinely feels this way and wants to get started in coding, I highly recommend doing one of the mooc.fi courses. Codecademy is fine as a taster/refresh but don't waste money on the premium when something like mooc is available for free.
I've tried to run the ide twice, once years ago on windows and once in fedora, where I needed to install snap to be able to install the ide and neither time I was able to get it to work.
Never heard of that site but looks cool, thanks!
I'm a systems administrator but I'm always looking for ways to expand my skill set, thanks for pointing me towards these awesome courses.
Programming is self-harm that has positive outcomes.
Can't I just take a magic potion?
I mean, coffee can help
Brilliant! Also tell them about chatgpt.
In my experience, ChatGPT has been wrong so many times that it's wasted more of my time than saved it.
So much this. I spent probably 2 hours try to get something to work that it said would work before giving up, spending 5 minutes to Google and finding the solution that I could use to get what I wanted done and more.
After that I rarely ask it for help.