#beginner programmer

[creative-crystal13]

first few lines of pygame 𖹭 16/03/2025

i have a friend who's helping me learn how to code, specifically in pygame and last night we played around a bit with the very basics and this is what he helped me write. it's not much but it's better than not having created anything. i'm still a long way to go but i am proud of myself for taking the initiative into creating more.

[y0ud0ntkn0wwh0]

Just started learning c++, tell you how it goes!

[dudewtheconfessions]

I just started learning programming.

For now it's just a finished labyrinth and a walking stickman animation in scratch but I am quite proud.

[sludge-code]

A rough start.

Hello! My name is Sludge and I'm a 17 year old girl who is trying to learn how to code. Shit's hard man. About a month or so ago I dipped my toes into Python and was enjoying it but realized I wanted to take a more structured, formal approach. I applied at my local community college and I'm now learning C. At this point I definitely know more in C than I did in Python, though it is quite a deal more confusing. I honestly kind of like the sharp learning curve. I do still feel like a fish out of water pretty consistently but it seems like thats pretty normal. I'm going to do my best to (somewhat) document my learning journey on here. Partially just so I can look back and feel proud and partially because I want an excuse to actually use tumblr aside from scrolling endlessly. I'm really not exactly sure what I'm going to post about. Maybe I'll just post random projects or exercises I do? If anyone has ideas for me, please comment or DM me. (that is, if anyone even sees this). Well, I suppose that's it. I'll talk to you all soon. - Sludge

[the-pasta-project]

Finally got to coding!!!! Sure, html isn't programming, but it's close enough for now!!

Also sidenote, trying to figure out the command line is alot more fun when you make it the classic hacker color scheme :)

[thirty4miracles]

y no umineko on ds? :( so sad

[readers-folly]

python will be the death of me

[golmac]

Inform Basics: ACTIONS and RULES

Note: this is a longer post than usual, but some of it is debug content that isn't required reading.

I've been promising to talk about debugging for a long time. And, in truth, figuring out disambiguation problems with the TRACE command is debugging. But since you may not have known the term disambiguation a couple of weeks ago, that's probably not what you had in mind.

No, you were probably thinking about some hardcore, silly weirdness in your game, some very hard to pinpoint problem. Today's post is about that kind of thing. We've talked about action processing. The events of a player's turn happen in a set order. We deal with that in the actions we define. The order is, first to last:

Before

Instead

Check

Carry Out

After

Report

Of course, there are things that happen outside of these phases. For instance, if we create an EVERY TURN rule, those fire at the very end of the turn, after report rules have been processed. In the course of play, players don't have a lot of insight into the various machineries of an Inform 7 turn. A lot of it is there just to keep Inform 7 being a thing at runtime, and that doesn't interest us. There's a very complicated mapping of the turn's processes, but I think it would just discourage beginners from trying to write IF at all. So let's not. Most Inform 7 stuff just works, and that's why I like it.

Still, at times there will be a head scratcher. When that happens, we have two tools that can help us figure out what's going on. The first is ACTIONS. Let's say we have a nice, juicy 50,000-word game, and one of our testers gives us a transcript in which "jump" isn't working properly. Instead, the jump command is printing a description of the room. With ACTIONS on (just type "actions" at the command prompt in a test environment), Inform 7 will print the specific actions being attempted and let us know if they succeed or fail.

Under default conditions, with JUMP working as expected, that would look like this:

>actions Actions listing on. >jump [jumping] You jump on the spot. [jumping - succeeded]

The text in brackets is the debug content toggled by ACTIONS. If we've set actions that interfere with jumping.... well, let's look at this code as an example.

Before jumping in the lab: say "Look before you leap!". Instead of jumping: try looking.

OK, so the BEFORE is specific to the lab, but the INSTEAD applies to the entire game world. So we must have forgotten something somewhere. We can use the ACTIONS command to have a look:

>actions Actions listing on. >jump [jumping] Look before you leap!

[(1) looking] lab nice lab.

[(1) looking - succeeded]

[jumping - failed]

This gives us something to chase after! This is a pretty simple example, but ACTIONS is most useful for helping us find problems once we get to a certain level of complexity in our game world. In this example, we can see that jumping "failed" and that looking "succeeded." By "failed," we know the jumping action never completed. Most commonly, that will be caused by an "instead" rule--they stop actions from continuing, right? A control-f on "instead of jumping" is probably in order.

But what if something more devious is at work? What about a case where the ACTIONS command doesn't report anything unusual? The next step is the RULES command, which is a verbose listing of every rule that fires in the course of executing a command. Now, as I said at the start of today's post, a lot of those rules are really none of our business. Their strangeness can be intimidating when reviewing the output in RULES mode. My advice is just not to worry about it. Just like the TRACE command, only a handful is likely relevant to us, so don't pressure yourself to figure it all out.

Though by all means do, if you're curious. Just don't be bothered by it.

So brace yourself, I'm going to print the output. I'm only going to talk about the pink text, so don't worry too much about the rest. I just want you to know what you're looking for.

>rules Rules tracing now switched on. Type "rules off" to switch it off again, or "rules all" to include even rules which do not apply.

[Rule "parse command rule" applies.]

>jump [Rule "declare everything initially unmentioned rule" applies.] [Rule "generate action rule" applies.] [Rule "announce items from multiple object lists rule" applies.] [Rule "set pronouns from items from multiple object lists rule" applies.] [Rule "before stage rule" applies.] [Rule "basic visibility rule" applies.] [Rule "basic accessibility rule" applies.] [Rule "carrying requirements rule" applies.] [Rule "instead stage rule" applies.] [Rule "requested actions require persuasion rule" applies.] [Rule "carry out requested actions rule" applies.] [Rule "descend to specific action-processing rule" applies.] [Rule "work out details of specific action rule" applies.] [Rule "investigate player's awareness before action rule" applies.] [Rule "player aware of his own actions rule" applies.] [Rule "check stage rule" applies.] [Rule "carry out stage rule" applies.] [Rule "carry out jumping" applies.] nice lab.

[Rule "after stage rule" applies.] [Rule "investigate player's awareness after action rule" applies.] [Rule "report stage rule" applies.] [Rule "report jumping rule" applies.] You jump on the spot. [Rule "last specific action-processing rule" applies.]

[Rule "A first turn sequence rule" applies.] [Rule "scene change machinery rule" applies.] [Rule "every turn stage rule" applies.] [Rule "timed events rule" applies.] [Rule "advance time rule" applies.] [Rule "update chronological records rule" applies.] [Rule "A last turn sequence rule" applies.] [Rule "scene change machinery rule" applies.] [Rule "adjust light rule" applies.] [Rule "note object acquisitions rule" applies.] [Rule "notify score changes rule" applies.] [Rule "parse command rule" applies.]

So you'll see in there the text that's been troubling us. That's "nice lab," which is the room description of the lab. We can usually start by looking at the rule immediately above the output. In this case, that's the "carry out jumping" rule. Hm, ok, so let's do a ctrl-f on "carry out jumping." We'll find this:

carry out jumping: print the location's description.

What a strange bit of code! Who knows why we did it. This is why I recommend giving names to particularly experimental or impactful rules. They are printed by names during a RULES debug session. So this code:

carry out jumping (this is the dubious jumping rule): print the location's description.

Will look like this in debug:

[Rule "dubious jumping rule" applies.]

The main thing to take from all of this is this: these tools can help you understand what Inform 7 is doing with a command. Like most debug content, you don't need to understand all of it, you just need to know what you're looking for. Usually, that's going to be some or all of the output that the player is seeing. Hopefully, that information will lead to a productive search of your code. I personally found the output from RULES intimidating; I gave myself permission to only understand what I needed to understand.

OK, next time, some lighter fare. We'll look at other useful commands and features for developers and testers.

[captainbrookeworm]

I will never learn to cut my losses with an animation because I would simply rather spend two hours re-learning blender just to get a 5 second shot

[rainbowcrowley]

another internship! a short one (4 weeks)! it's going much better than the previous one! i have to learn javascript! it's fun! but oh my god the pressure is real lmao learning a new programming language from scratch is no easy feast gkjdlgdgd

[zintblog34]

How to start your career as a coder - guidance of programming for beginners

As we know , the new generation is becoming so advanced with technology. With technology we can do a number of things in less time and effort. Now, learning to code is also a significant part of technology. We can say that coding is an important part of technology. It is a basic and demanding skill for any company which wants to be part of this digital world. 

Here are some significant topics that are discussed to become a good coder -.  

1.Find out why you want to learn to code- 

Before you start studying, think about why you want to learn to code. Think clearly with full focus what thing you  want to learn in coding and why. It is too much. After entering there are many parts available which you can explore.

2.Make a great choice in choosing which coding language for you want to go -

In coding, there are too many programming languages which you can learn but learning each language is a difficult task. As a beginner, you can go with HTML or CSS programming languages which do not contain data structure and algorithms.                                                            

3.Selecting Best coding bootcamps -

           Coding bootcamps are educational programs which are made for development of practical skills. While the institute will different for each bootcamps, you can typically expect to learn:

Programming fundamentals like javascript, CSS and HTML.

Languages which are popular like java, python or C.

Web development.

HTML codes for website development.

4.How to choose a coding bootcamp-

There are various important things which you can remember while choosing a good coding bootcamp -

Learning format - Both online and offline mode for learning is available. You should choose which environment is suitable for you. In online mode you can take classes according to your needs. And in offline mode you get a chance to interact face to face. 

Cost - As we discussed earlier, coding bootcamps can be expensive. You should think about how much you have to spend and how much you want to spend on bootcamps. 

5.Benefits of joining a coding bootcamp-

 Boost your salary potential -  

 In technical professions, demand is increasing with time in comparison to other professions. For software developers, new opportunities are increasing day by day. Now,any tech professional can join any field and department according to their interest. 

Expand your career possibilities - 

The best advantage to join a coding bootcamp is you can increase your skill level. You can learn any new thing with the help of that. The following list details some of the more common jobs you may be able to get after your finish a bootcamp:

1. Back - end developer 

2. Full - stack developer 

3. Junior developer 

4. Software engineer 

5. Application developer 

6. And so on 

[mityenka]

Hi! I know nothing about politic (my parents never really cared and I always felt too dumb to ask other people) but I always wanted to learn more about it, do you have any recommendations I can read for beginners? Like, where can I start?

hi anon no problem, i'm not sure if i'm the best person to ask this because i also just started really engaging with theory like a year ago but i answered a similar question some time ago in this post, i hope this helps!

[geekonik]

Latest in Tech and Programming.

Who We Are

Welcome to Geekonik, your go-to platform for mastering the latest in tech and programming. Whether you’re a beginner eager to start your coding journey or an experienced developer looking to sharpen your skills, we offer a diverse range of expert-led courses designed to help you succeed in today’s ever-evolving tech industry.

Let the Numbers Speak

✅ 200+ Courses

✅ 30+ Expert Instructors

✅ 4000+ Students and Growing

Our Vision

At Geekonik, we believe learning tech should be both practical and enjoyable. That’s why our curriculum is constantly updated to reflect the latest trends, technologies, and best practices. Join us today and take the first step toward becoming a skilled programmer or tech professional!

Our Mission

Our mission is simple: to make technology and programming education accessible, engaging, and impactful for learners of all backgrounds. We are committed to equipping individuals with the skills and knowledge they need to thrive in the digital world.

Through hands-on projects, expert-led courses, and a collaborative learning environment, we inspire curiosity, foster growth, and empower the next generation of tech professionals. Our goal is to bridge the gap between learning and real-world application, ensuring our students are ready to tackle the challenges and opportunities of the future.

Success Stories

🚀 "Geekonik transformed my career! I went from zero coding experience to landing my first developer job in just six months. The hands-on projects made all the difference!" – Alex R., Software Engineer

Join the Geekonik community today and start building the future of tech—one skill at a time!

Call Us

+91 9560562455

Our Location

H140 Fourth Floor Sector 63 Noida

Website 

[stuintern23]

Learn Data Science with Online Courses and Certification | StuIntern

Take the first step toward becoming a data expert with StuIntern’s Data Science Programs. Whether you're a beginner or advancing your skills, our data science course for beginners offers a clear path to success. Explore our data science online course and earn a valuable data analyst certificate to boost your career. With comprehensive data science course details and hands-on learning, you'll gain the knowledge to thrive in this fast-growing field. Start today and learn to be a data scientist with StuIntern!

[appcurators]

Mastering Git Configurations: The Three Essential Levels!

System Level: Configures preferences globally on your machine. Useful for applying settings to all users and all projects on your computer. Adjustments here affect Git's core system settings.

Global Level: Specific to your user profile. This is ideal for settings like your username and email, which are specific to your contributions across projects.

Local Level: Specific to a single project. Overrides system and user settings for individual project preferences. Perfect for project-specific configurations.

Dive deeper into each level to optimize your Git setup for streamlined and efficient workflow!

#GitConfig #DeveloperTools #TechTips #CodingLife #SoftwareDevelopment #VersionControl #GitTips #ProgrammingBasics #TechCommunity #CodeNewbie