Programming

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Python could be so much better if it had a better ecosystem.

That, or Microsoft could just get off their asses and make ironpython a thing again so that I can have Python.NET.
 
<programming>
<hacking class="4chan">
<DDoS src="https://www.pentagon.gov">
</hacking>
</programming>

I'm not exactly a leet haxor, but I do consider myself a hacker.
 
Coming from a C background, object orientation still confuses the hell out of me sometimes.
 
I've considered learning C (basically from knowing very little aside from scripting), is the K&R book still considered a good resource for C programming? Or is C even worth learning above anything at the moment?
 
I've considered learning C (basically from knowing very little aside from scripting), is the K&R book still considered a good resource for C programming? Or is C even worth learning above anything at the moment?
what languages do you know?
 
I've considered learning C (basically from knowing very little aside from scripting), is the K&R book still considered a good resource for C programming? Or is C even worth learning above anything at the moment?

K&R is still the authoritative resource from the creators of the language itself. However, if you have limited experience programming, C is the hard road.

It's worth learning if you want to do embedded systems programming (Arduino) or kernel programming. It also has some valuable skills you can carry over to C++, which is primarily used in games. Web stuff is rapidly transitioning to full-stack Javascript frameworks.

Coming from a C background, object orientation still confuses the hell out of me sometimes.

Object orientation (which can be done in C, I must add) is just about putting things in boxes. It is the intersection of two programming concepts: encapsulation, which groups related data and functions together in a single unit, and inheritance, which enables hierarchical code reuse. Each of these boxes manages its own thing, and nothing more. For example, in my ROM downloader platform, I have a "box" that does nothing more than load tiles and palettes into the console VDP, and a "box" that does nothing more than create an on-screen view using those tiles. Programming then becomes about connecting these independent components together, much like making connections between electrical components. It enforces code reuse and strict separation of concerns. I've done almost all my programming object-oriented, so programming without it is rather alien to me.
 
Last edited:
I want to learn programming but my course only taught the very basics of Java so far. The most complicated thing we got to work with so far are arrays. Kinda disappointing.
 
I want to learn programming but my course only taught the very basics of Java so far. The most complicated thing we got to work with so far are arrays. Kinda disappointing.
The internet is a great thing- there are a lot of good resources for learning programming online now including things like Stackoverflow and various language-specific/IDE-specific forums.
 
reported for hacking ! !
Good_Luck_I_m_Behind_7_Proxies.jpg
 
Oh god, absolutely.

Stuff like single letter variables and a giant web of obscurely named functions with setjmp/longjmp scattered everywhere. Yes, yes, I'm sure the performance is absolutely boner inducing. And I'm also sure the guy's remaining coworkers are going to have fun debugging that after the author gets fired.

That's not rainman-like brilliance. That's rainman-like going-to-fuck-the-company...ance.
I haven't seen this stuff in ages. But a lot of strange programming used to come from isolated programmers back in the day, reinventing wheels and just really strange ways of getting things done. It's a shame actually that most of that shit will never see the light of day now some of it is really interesting. I have an embarrassing set of floppy images and its just so cool to look through it.

Yep, that's one of the basics we were repeatedly (always) taught when I was studying programming- make sure your variable and function names clearly indicate what the hell they actually do/represent, and try and avoid needless spaghetti code. Some people just seem to forget that as soon as they get into the industry though >.>
It used to be common that varible names could only be 8 bytes or so and then for a variety of reasons it remained fashionable to code like a fgt for n yrs aftr tht
 
Last edited by a moderator:
  • Agree
Reactions: Splendid
[Marvin: That's not rainman-like brilliance. That's rainman-like going-to-fuck-the-company...ance.]

I haven't seen this stuff in ages. But a lot of strange programming used to come from isolated programmers back in the day, reinventing wheels and just really strange ways of getting things done.

Perhaps that's Rainman-like you-can't-fire-me-because-nobody-else-knows-how-this-works.
 
  • Agree
Reactions: Marvin
I'm in college right now and they stress to the point of failing code that cannot be deciphered by the layman; any variable or method that isn't self explained will lose you marks. They do tell of code (I've heard NASA are guilty of this) which hasn't been improved since the 70's because nobody wants to touch it. But I assume your code has to be explainable these days. I was working with PhD's for a Java intern this year and I was constantly asking them questions about the code I was working with
 
Back