Why did the chicken cross the road?

Assembler Chicken: First, it builds the road ......

C Chicken: It crosses the road without looking both ways.

C++ Chicken: The chicken wouldn't have to cross the road, you' d simply refer to him on the other side.

COBOL Chicken: 0001-CHICKEN-CROSSING.
IF NO-MORE-VEHICLES
THEN PERFORM 0010-CROSS-THE-ROAD
VARYING STEPS FROM 1 BY 1 UNTIL
ON-THE-OTHER-SIDE
ELSE
GO TO 0001-CHICKEN-CROSSING

Cray Chicken: Crosses faster than any other chicken, but if you don't dip it in liquid nitrogen first, it arrives on the other side frazzled.

Delphi Chicken: The chicken is dragged across the road and dropped on the other side.

Gopher Chicken: Tried to run but got beaten by the Web chicken.

Intel Pentium Chicken: The chicken crossed 4.9999978 times.

Iomega Chicken: The chicken should have ' backed up' before crossing.

Java Chicken: If your road needs to be crossed by a chicken, then the server will download one to the other side. (Of course, those are chicklets.) See also WMI Monitor.

Linux Chicken: Don't you *dare* try to cross the road the same way we do!

Mac Chicken: No reasonable chicken owner would want a chicken to cross the road, so there's no way to tell it how to cross the road.

Newton Chicken: Can't cluck, can't fly, and can't lay eggs, but you can carry it across the road in your pocket.

OOP Chicken: It doesn't need to cross the road, it just sends a message.

OS/2 Chicken: It crossed the road in style years ago, but it was so quiet that nobody noticed.

Microsoft's Chicken: It's already on both sides of the road. What's more its just bought the road.

Windows 95 Chicken: You see different coloured feathers while it crosses, but when you cook it still tastes like........ chicken.

Quantum Logic Chicken: The chicken is distributed probabilistically on all sides of the road until you observe it on the side of your choice.

VB Chicken: USHighways! <TheRoad.cross> (aChicken)

XP Chicken Jumps out onto the road, turns right, and just keeps on running.

The Longhorn Chicken had an identity crisis and is now calling itself Vista.

The Vista Chicken dazzled itself with its own graphics.

Anyone looking for something interesting to do???

Step 1) understand how basic circuitry works on a bread board nothing too fancy. ( Implement NAND, AND, ADDER, SUBTRACTOR)

Step 2) learn about microprocessors and how OS works

Step 3) learn assembly

Step 4)write a basic assembler and understand how loaders and linkers works !

Step 5) write a kernel with very basic features like memory management and process management and some drivers for IO

Step 5) write an emulator for some simple systems .! ex chip-8.

Step 6) read about compiler theory and automata

Step 7) write a basic Python interpreter that compiles (not interpreter) to native assembly.

Step 8) implement TCP stack .

Step 9) learn as much as u can about complexity measurement ), data structures and algorithms using C or C++ it's very important ( familiarity with pointers and thus computer memory )

Step 10) learn any high level language of choice like Python or Ruby.

Step 11) stop debating over tabs vs spaces , emacs vs vim , angular vs vue, php vs Python , OOps vs procedular vs functional ( just know about all of them and when to use but don't fucking debate over which one is superior )..

Step 12) live happily and be healthy.

Writing an assembler for my final.

"OK, good, now I just need to make the program write the output file. That shouldn't be hard."

*5days later*
"Fuck."

Chuck Norris can do Web Development in Assembler.

Impostor vs Kenner syndrome

We got a new kid which does his internship from school. We talked and he asked me what stuff I had done with 14 - 16. I remembered with 14 I was really into reverse engineering, assembler and c/c++ but never managed to actually build something.

So he started to say stuff like he could replace me in an instant and he should get paid for this internship at least as much as I did, because he made some websites and games already.

I really was down. Kids today get a lot of shit done and I was a disappointing lazy little shit just playing games and try to reverse engineer stuff and learn assembler and c++.

It's been month and shit hit me when I've seen his stuff was copy pasted from a tutorial/ YouTube video.

Today's ressources, languages, frameworks make it really easy to build something but I still got respect for everyone every age who is interested and get into programming and stuff.

But I hope you'll read this you little shit and realise that you can use a simple physics engine by copy and pasting code. So don't talk disrespectful to people in general especially when they can create a whole game and physics engine.

hmnn..

Anyone remember win32? Here is a cheat sheet for classy devs

A memorial for my favorite rant of all time "Why did the chicken cross the road?"

+++++++++++++++++++++++++++++++++++++

Why did the chicken cross the road?

Assembler Chicken: First, it builds the road ......

C Chicken: It crosses the road without looking both ways.

C++ Chicken: The chicken wouldn't have to cross the road, you' d simply refer to him on the other side.

COBOL Chicken: 0001-CHICKEN-CROSSING.
IF NO-MORE-VEHICLES
THEN PERFORM 0010-CROSS-THE-ROAD
VARYING STEPS FROM 1 BY 1 UNTIL
ON-THE-OTHER-SIDE
ELSE
GO TO 0001-CHICKEN-CROSSING

Cray Chicken: Crosses faster than any other chicken, but if you don't dip it in liquid nitrogen first, it arrives on the other side frazzled.

Delphi Chicken: The chicken is dragged across the road and dropped on the other side.

Gopher Chicken: Tried to run but got beaten by the Web chicken.

Intel Pentium Chicken: The chicken crossed 4.9999978 times.

Iomega Chicken: The chicken should have ' backed up' before crossing.

Java Chicken: If your road needs to be crossed by a chicken, then the server will download one to the other side. (Of course, those are chicklets.) See also WMI Monitor.

Linux Chicken: Don't you *dare* try to cross the road the same way we do!

Mac Chicken: No reasonable chicken owner would want a chicken to cross the road, so there's no way to tell it how to cross the road.

Newton Chicken: Can't cluck, can't fly, and can't lay eggs, but you can carry it across the road in your pocket.

OOP Chicken: It doesn't need to cross the road, it just sends a message.

OS/2 Chicken: It crossed the road in style years ago, but it was so quiet that nobody noticed.

Microsoft's Chicken: It's already on both sides of the road. What's more its just bought the road.

Windows 95 Chicken: You see different coloured feathers while it crosses, but when you cook it still tastes like........ chicken.

Quantum Logic Chicken: The chicken is distributed probabilistically on all sides of the road until you observe it on the side of your choice.

VB Chicken: USHighways! <TheRoad.cross> (aChicken)

XP Chicken Jumps out onto the road, turns right, and just keeps on running.

The Longhorn Chicken had an identity crisis and is now calling itself Vista.

The Vista Chicken dazzled itself with its own graphics.

writing an assembler for my compiler, Manticore.

Currently working on writing a hand written parser and parse tree node system.

Good morning everyone (atleast for my Time Zone), god bless you all !

been following my morning silly brain for 3 hours to write an 8086 assembler CPU and RAM emulator. after 1 hour of debugging, time to polish it and refactoring.

Ok. Yesterday I finished building my compiler I have to say: it was a pretty darn big thing with 7000 Lines of code.

I did it alone and with almost no help.

I wanted to give some advice in case someone wants to program a compiler. I knaw its useless in times of lex and yacc, but anyway.

-have a good idea for the language
-learn about parser/lexer
-learn assembler
-do it like me: output the assembler to a file and let it assemble/link by the linux standart-tools (call the commands)
-Have fun. Fun is essential in coding

I hope I was able to help people who want to build a compiler alone... Yau can always ask questions ;~)
-

Programming Languages are Like Cars:

Assembler: A formula I race car. Very fast but difficult to drive and maintain.

FORTRAN II: A Model T Ford. Once it was the king of the road.

FORTRAN IV: A Model A Ford.

FORTRAN 77: a six-cylinder Ford Fairlane with standard transmission and no seat belts.

COBOL: A delivery van. It's bulky and ugly but it does the work.

BASIC: A second-hand Rambler with a rebuilt engine and patched upholstery. Your dad bought it for you to learn to drive. You'll ditch it as soon as you can afford a new one.

PL/I: A Cadillac convertible with automatic transmission, a two-tone paint job, white-wall tires, chrome exhaust pipes, and fuzzy dice hanging in the windshield.

C++: A black Firebird, the all macho car. Comes with optional seatbelt (lint) and optional fuzz buster (escape to assembler).

ALGOL 60: An Austin Mini. Boy that's a small car.

ALGOL 68: An Aston Martin. An impressive car but not just anyone can drive it.

Pascal: A Volkswagon Beetle. It's small but sturdy. Was once popular with intellectual types.

liSP: An electric car. It's simple but slow. Seat belts are not available.

PROLOG/LUCID: Prototype concept cars.

FORTH: A go-cart.

LOGO: A kiddie's replica of a Rolls Royce. Comes with a real engine and a working horn.

APL: A double-decker bus. It takes rows and columns of passengers to the same place all at the same time but it drives only in reverse and is instrumented in Greek.
Ada: An army-green Mercedes-Benz staff car. Power steering, power brakes, and automatic transmission are standard. No other colors or options are available. If it's good enough for generals, it's good enough for you.

Java: All-terrain very slow vehicle.

Soooo I think I have finally come to the point that I may have to create a YouTube channel, to teach software engineering from the ground up... and teach it the way the universities and everyone else should be teaching it, so that they have a solid foundation.... throwing hello world, and loops and variables at folks out of the box without any of the environment context or low level embedded register, even logic gate understanding

That lack of understanding is why, soooo many college students and younger folks, are actually pretty shitty engineers. Everything is high level languages and theoretical concepts to them. Nothing practical, that’s why there’s sooo many python and java developers that can’t for the life of them understand memory management, low level hardware interfacing etc, because the colleges don’t teach it the way it use to be taught.

I seriously fear 30 years from now or sooner when there are few embedded engineers only left till retirement, as without those folks the whole pyramid of electronics falls to pieces.

Java, C#, python, all that shit don’t run on the bare metal... there’s this magical layer of C, and assembler that does all the work just so folks can abstract their thoughts.

Either 1 of two situations will happen.. price of electronics will rise because the embedded guys are few and far between therefore salaries skyrocket... OR everything starts running shit like java on the metal, where there are a over abundance of developers, their salaries will be low because there are soo many but the processing power, space, and energy needed to run java natively causes electronics cost to increase

but regardless 30 years from now if those script kiddies are building everything I fear it cuz there’s gonna be memory leaks, and overflow issues everywhere.. shit be blowing up more than 4th of July.. lol

Soooo in effort to prevent that and keep the embedded engineers up, or atleast properly educate the script kiddies, I’m gonna make that YouTube channel.. 1 maybe 2 videos a week, 1-2 hours sessions each.. starting at the fucken ground and building up.

Me taking the first steps in Assembler

1986. Commodore 64 computer. First program in assembler to move cursor on screen. I will never forget that day.

I started programming 7 years ago, but I downloaded my first tutorials on programming in C++ already back in 2000. I had read maybe 4 pieces of literature, didn't understand anything, because it taught things in this order 1, "So, say you want to create a cat?", no I don't. I want to make a useful program.
2, "then you have make a constructor and a destructor", makes sense since that perfectly replicates nature, not,
3, "then you can define a method in the class that enables your cat to meow", eeeh no it doesn't make a sound, what it does however is print a series of characters even less useful than "Hello World" to stdout.

Then I found assembler and it all made sense! 😀

Assembly:
"OMG! What an unfriendly language! It's so obsolete!"
WebAssembly:
"OMG! Assembly is on the web! It's so amazing!"

Real men write code in Assembler!

Web development in assembler.

So recently I did a lot of research into the internals of Computers and CPUs.
And i'd like to share a result of mine.

First of all, take some time to look at the code down below. You see two assembler codes and two command lines.

The Assembler code is designed to test how the instructions "enter" and "leave" compare to manually doing what they are shortened to.

Enter and leave create a new Stackframe: this means, that they create a new temporary stack. The stack is where local variables are put to by the compiler. On the right side, you can see how I create my own stack by using

push rbp
mov rbp, rsp
sub rsp, 0

(I won't get into details behind why that works).

Okay. Why is this even relevant?
Well: there is the assumption that enter and leave are very slow. This is due to raw numbers:
In some paper I saw ( I couldn't find the link, i'm sorry), enter was said to use up 12 CPU cycles, while the manual stacking would require 3 (push + mov + sub => 1 + 1 + 1).

When I compile an empty function, I get pretty much what you'd expect just from the raw numbers of CPU cycles.

HOWEVER, then I add the dummy code in the middle:

mov eax, 123
add eax, 123543
mov ebx, 234
div ebx

and magically - both sides have the same result.

Why????

For one thing, there is CPU prefetching. This is the CPU loading in ram before its done executing the current instruction (this is how anti-debugger code works, btw. Might make another rant on that). Then there is the fact that the CPU usually starts work on the next instruction while the current instruction is processing IFF the register currently involved isnt involved in the next instruction (that would cause a lot of synchronisation problems). Now notice, that the CPU can't do any of that when manually entering and leaving. It can only start doing the mov eax, 1234 while performing the sub rsp, 0.

----------------

NOW: notice that the code on the right didn't take any precautions like making sure that the stack is big enough. If you sub too much stack at once, the stack will be exhausted, thats what we call a stack overflow. enter implements checks for that, and emits an interrupt if there is a SO (take this with a grain of salt, I couldn't find a resource backing this up). There are another type of checks I don't fully get (stack level checks) so I'd rather not make a fool of myself by writing about them.

Because of all those reasons I think that compilers should start using enter and leave again.

========

This post showed very well that bare numbers can often mislead.

Googles definition of assembler in germany: "a simple programming language" ... Seems legit

Back to the fundamentals 😅

It was 1986. I'd just bought a computer because I wanted to make a cool flight sim like I saw a friend at school do by typing in a bunch of code from a magazine. I read a thick book on DOS/BASIC and another on Assembler. As I had no idea what Assembler could possibly be useful for in my life, I went the DOS/BASIC route and made some fun programs. Then it was Prolog followed by C and Smalltalk and then HTML and JavaScript. All by taking classes or reading books and then making something useful or teaching others.

Studying AVR Assembler in university *cries in binary*

1. Finish 8bit computer
2. Program an assembler
3. Find a girl friend

Can you guess which one will be in my new years resolution next your too?

Just talked to a guy who codes microcontrolers in assembler. He wants to use a raspberry pi as an interface device between TCP and Serial port. He asked me how fast that would run over internet and I told him that it depends on the connection an other things it takes at least some milli secs to transmit.
He is like:
What the fuck do you mean milli secs?
I poll data on my 20 mhz controler every like micro sec or so and that Pi got 1Ghz.

Me like: Yea go fucking code that shit on your own with ASM.

> Advice to new coders

Don't worry over picking language A or B.
Just pick A, use it for a month, then move on to B.
In a normal 3 year college degree you'll try multiple languages, some of which you'll never use again, and they'll each teach you something.

I had classes in Java, C, C++, C#, Prolog, Assembler, F#, JS.

Never used F# again and no one uses Prolog. But they were great for learning recursion and logic.

It's not like you take "a step down a bad path" if you pick a language you're never gonna use again.

You'll also learn new stuff on the job. We have one team that uses Go and one that uses Rust. None of the devs ever studied those languages. They were mostly former Java devs who leaned on the job.

It’s throw back Thursday!

Back to 1979... before the time of the red dragon book compiler book, (forgetting about the green dragon book) ... there was a time where only a few well written compiler and assembler “theory” books existed.

What’s special about this one? Well Calingaert was the co patentor of the OS/360. .. “okay soo? ... well Fred Brook’s Mythical Man-Month book I posted the other day. Calingaert is basically the counterpart of brooks on the OS/360.

Anyway, the code is in assembly (obviously) and the compiler code is basic.

Other than this book and from my understanding 2-3 other books that’s all that was available on compilers and assemblers as far as books written goes at the token.

ALLL the rest of knowledge for compilers existed in the ACM and other computing journals of the time.

Is this book relevant today, eh not really, other than giving prospective, it’s a short in comparison to the red dragon books.

If you did read it, it’s more of a book that gives you more lecture and background and concepts.. rather than here’s a swath of code.. copy it and run.. done.. nope didn’t happen in this book.. apply what you lean here

Minecraft mods get me into programming. I used to spend hours yelling at Eclipse for not making that stupid JAR file! 7 years later, I'm pursuing a career as someone who spends hours yelling at a CLI assembler for not making that stupid ISO file! Good times.

Here is another rather big example of how C++ is WAY slower than assembler (picture)

Sure - std::copy is convenient
but asm is just way faster.
This code should be compatible with EVERY x86_64 CPU.

I even do duffs device without having the loop:
the loop happens in the rep opcode which allows for prefetching (meaning that it doesnt destroy the prefetch queue and can even allow for preprocessing).

BTW: for those who commented on my comment porn last time: I made sure to satisfy your cravings ;-)

To those who can't make sense of my command line:

C++ 1m24s
ASM 19s

To those who tell me to call clang with -o<something>:
1) clang removes the call to copy on o3 or o2
2) the result isnt better in o1 (well... one second but that might be due to so many other things, and even if... one second isn't that much)

Not quite a interview question, but in a competition (I had build a compiler) the jury (they all told me they had all studied informatics) asked me what a compiler is... Not in a "lets try to catch him off manner" but rather in a "i am too stupid for this world manner" he asked me what a compiler was... And it got even worse: my compiler is based on linuxes utils (nasm+ld) the guy didnt know about linux. Assembler was much too much for him and when my compiler threw an error (I wanted to show them the error system) he told me I shouldnt present unfinished projects... Atleastthe other two were really nice and i still got 2nd place (behind a person who prorammed an Nxt thingy)

I confess that I know how to manage memory on assembly language, but I never knew how to use the memory button of my Casio calculator :'v Should I be ashamed?

Do arcade games (Pac-Man, Donkey Kong, Berserk) count? I got my allowance in quarters.

Atari 2600? Ti/99 with a tape drive to play a game at my friend's house?

Having to buy a 5.25" floppy in the HS bookstore for typing class on the TRaSh-80s and finding a way to put a break in the program and save it to disk so I got top score on assignments?

Tron. That's what really did it for me. To this day, I like to imagine there is a vast world inside the computer.

After a BASIC programming class in HS, I got an Apple IIGS and started writing my own load menus for these little games I'd find around FIDO and newsgroups. Instead of "PR#6, brun gumball" a nice styled menu would show where you could press the number of the game you wanted to play.

I bought a book on Apple assembler and promptly got disillusioned with full blown programming (in 1988), instead sticking to BASIC and, later, JavaScript, HTML, PHP, CSS, and Python.

Who remembers sharing hacked PCP accounts to dial out of state BBSes?

Applied Engineering customers and 300 baud chatroom lurkers represent.

User #243, God's Country chat

The guy Intel hired to come up with instruction mnemonics must be just letting his cat walk over the keyboard every time he needs a new idea.

cvttps2dq? sounds good!

It was 1987. I was 13. My first dev project started with a $1,300 IBM PC XT clone I bought from a relative who was a “dealer” of PCs for some company. It took all the savings I had from birthday money and mowing lawns for several summers at $5 a pop.

My mom wanted to encourage me to learn it more in depth, and she also wanted to know more for her job as a librarian, so she bought us a bunch of books about DOS, BASIC, and Assembler.

I first got familiar with DOS and then dove into Assembler without realizing what it really was (and how much easier BASIC would be). After hours and hours of typing in what, to me, then, was complete gibberish, I grabbed the BASIC book to see what it had to offer.

I never went back to the Assembler book.

A kid at school had given me a BASIC program he had typed in from a magazine. It was a flight simulator of sorts but with a helicopter, IIRC. I loaded up that bad boy and got to hacking. I didn’t get much done with it but I did build a few other menu navigation programs to explore the language more.

That led to PROLOG, C, PASCAL, Visual Basic, Perl, ASP, ColdFusion, and now PHP.

My grandpa thougt me assembler when i was 7, I modded an hard drive with him (multiple write heads on one disc). Then i learned pascal. As my fathel work at sap, i got a free webdew course. And now, im "learning" c++ (rather sharpening my skills than learning)

Just finished an assignment yesterday where we had to code a math problem in assembler in under 20 lines

looking at the task: Hey, we already did this in Python

*building own modulo Operation for that cause we cant use it*

*freaking out when realizing it's just not posibble in 20 lines*

Then scrolling up the wikipedia page to see you've spend hours trying to implement the wrong thing

First job was coding voice alarm s Systems (1998) primarily using Delphi and programming act microcontrollers using avrco pascal and act assembler.

They were happy days

Saw a post in which some dude said that he lost his virginity to C++. Well, I got it the hard way - I actually lost mine to assembler.

Tried to reply to @Fast-Nop who had replied to someone wondering if C would be a good first language.

IMHO C should have been put to sleep ages ago. A few years ago I downloaded the latest, greatest C Standard. For a language billed as small and simple (by many) it was over 800 pages long. Still there's a lot that's unspecified like order of evaluation of function arguments. Int etc is implementation dependent. And error handling, let's not go there. The macro assembler throws away all the semantics leaving behind a cryptic value. It's a complex language due to the innumerable interactions possible.

It's been called assembly language for the PDP-11 minicomputer. Recently learned that even the VAX-1 was built from SSI chips like the 4-bit 74181 ALU. The VAX.

Anyway I had several excellent books on programming style written by Henry Ledgard. He despaired of making C look readable. I commend his books which are so old that the code is UPPERCASE A lot of he wrote had to do with program design, naming things, writing good comments and that the visual shape of a program assists mental clarity.

Can someone please forgive me for this mess?
Atleast its a fast mess.

(btw: I have no idea wether it works. I hope it does)

Sometimes I wonder how software development in (bigger) teams worked in the 90s.

Take the first Pokémon games for example. It was the mid-90s and the final product would be Assembler code that goes onto a cartridge with limited space.

I believe version control systems didn't really exist back then (Git & Mercurial: 2005, SVN: 2004). So probably people took backups of the chunks of code they worked on, copied around a stitched-together code, threw everything together at the end of the day, etc. etc. ...

Does anyone here know if there is some kind of documentary about that topic or did anyone here experience that first-hand?

It would be really interesting to see how that stuff worked back then 😊

People who confuse Assembler with the Assembly language...

to the guys saying "oop is dumb" / "i don't need oop" / "i've never worked with oop"...

i have some questions:
- which language are you working with
- which problems are you solving
- how big is your code base
- how do you maintain readability of your code?

don't get me wrong, i don't believe that oop is always the answer. i'm just curious which fields these statements are coming from. if they all come from a low level (assembler, C, ..) or functional languages or "scripty" languages (python, JS), or if there are also people working with languages like C++ where oop is pretty much established. and if the latter, i'm curious how people design their code and what problems they solve... tell me your story :D

Today on forgotten games – Vangers.

Even though the game is extremely hard and very, very frustrating, it somehow has an ability to make you obsessed with it. A very complex pieces of information, either carefully crafted or accidentally emerged from the void, delivered straight to your brain, making you an addict. If you play it and not delete it after five minutes, there is no way back – you better get used to new, different you.

There are many hard but addictive games based on simple mechanics, but Vangers is a different story. Compared to Vangers, Dark Souls seems nice, simple and easy casual game.

One can easily imagine "the hardest game possible", but all of them simply makes you delete the game and not to play it at all. Vangers precisely balance over this, achieving a very fragile equilibrium, being hard enough to frustrate you like no other game does, but not hard enough to simply make you quit instantly. While doing so, the game makes you a junkie, addicted to its eerie psychedelic nature.

This game spits in your face. This game makes you a slave, a desperate addict. All of your previous gaming skill, and speedrun experience doesn't matter.

The plot roughly goes like this: humans fucked up while experimenting with portals and accidentally discovered an advanced hivemind race. Trying to escape they fuck up spacetime and the two incompatible civilizations annihilate each other, creating a primal soup of creatures, from which the whole new world emerges. So there are many different strange creatures trying to survive in fucked spacetime where incompatible worlds are forcefully fused together, and you are the Vanger, one of many other Vangers trying to figure out what they are and how they was created.

The game features a voxel, fully-destructible world mapped on a torus. The game lore and terminology are extremely complex, and no one will explain it to you, you have to figure everything out yourself. Skip the dialog and no one will repeat it, you're on your own now.

Every playthrough is different. There are very many game mechanics and play styles available.

Everything in the game including complex rendering engine was written in C and Assembler back in 1998.

There are two types of Vangers players: the ones who was able to escape early and the ones who think that Vangers is the best game of all time. This says it all.

Last warning – DON'T PLAY THIS GAME. You better watch some playthrough on youtube.

Some 6502 Instructions by the legendary Beagle Bros 🖥💻

My parents (mom and grandma) helped me buy my first PC. I had some money saved from mowing lawns and they supplemented the rest. Mom, a library director, got a bunch of DOS and Assembler and BASIC books and encouraged me to teach myself.

That turned into computer camps and helping with tech at the library and school. That turned into a computer science and aerospace scholarship to college where I learned C and Unix.

That turned into a degree in business information systems and a career in web development.

19 more years to go and I can retire.

Taught myself assembler at 13 (this was the mid 1980s) and wondered how the hell people could stand to do this. Then I found out there were more abstract languages like BASIC or COBOL. So I taught myself BASIC and MS-DOS batch scripting. Various other languages came later (PROLOG, Pascal, C, Smalltalk, C++, VisualBasic, etc). But it’s never been easy for me because I suck at math and complicated logic structures. Especially not good with OOP. My brain was ruined by learning procedural coding first. It refuses to incorporate OOP.

Our team had a brilliant engineer, he made a tool that would convert IBM Assembler code to C, comments included. the comments are the assembler code. bleh

Writing assembler is so much fun /s

Just wondering, how many of you can actually code in assembly?

Adobe's ExtendScript toolkit is abyssmal. I find posts from 2008 referring to issues that have not changed even in CC2017. Do you think they are small issues I'm bitching about? I'll list 2. First, the toolkit only colours "var, return, for, foreach" and a bit more keywords and the strings, of course you can set up color schemes but those are limited and not colouring stuff. The second issue is auto-complete, it rarely kicks in and suggestions have 0 connection to what are you doing and are always the same. It doesn't recognize anything of what are you doing.

Probably in 2008 you had to program with the manual near you like writing assembler, now there's an improvement in 2017, they got a window named object browser or something like that that actually is a summarised portable manual that could've been easily transformed in auto-complete suggestions.

Adobe writes about this and I quote: "a complete integrated development environment". Although I will not write much scripts in it, I need to write a big one and thought about extracting that object data and putting it in a more capable javascript editor. LO and Behold what I discovered, the ExtendScript Toolkit that's supposed to edit Extended javascript and save it as jsx or jsxbin is almost completely (it has some dlls too) built using around 100 jsx files. It's the equivalent of building a js IDE to edit js.

Sorry for formatting, I'm on mobile, I tried.

Assembler for the win!

I'm not going to lie, the surge of bootcamps really irks me. Not because I'm afraid of competition, or that I'm an elitest. Mainly because a lot of people who attend these bootcamps have no real interest in software engineering. I sometimes attend a meetup, and it's a beginner meetup. I try to help out. And a lot of people clearly have no patience for learning software engineering. I try to be encouraging, but sometimes I just want to be dick and tell them "Why the hell do you want to be a dev, if you're not interested in how computers work".

I'm an 100% myself taught developer. Granted I'm 38 and taught myself programming at 14. But it came out of an earnest desire and love for technology in general. So I never shyed away from learning? C and assembler? Bring it on. Theoretical computer science? I can get with that. For me I loved computer so much, that I was willing to learn about anything in the realm of computing.

This is what annoys me with the adult bootcamp crowd. I feel they're only willing to learn as long as it's easy. If something gets complicated or complex, then they check out. And I a lot of their questions is "tell me how to do this/that". But they don't know why they would do it.

To me it feels like they're trying to fast track themselves to a dev job. Yet you would think if they're trying to do this all professionally, they would be open to learning as much as possible, and not closing themselves off.

My semi-friend who runs the meetup is trying to start a bootcamp himself. So I try I severely hold my tongue when I attend those meetups. And I want to be supportive. I certainly don't want to be the reason why people are turned off by programming. But at the same time, I hate how people are abusing this profession because they think it's fast money and an easy way to earn 6 figure salaries.

Wrote my first programs on my Commodore C64.
First program was a number guessing game where you needed to guess a number between 1 and 100. Shit had 300+ lines because I only new the if clause and the equals comparison.
I was 9.

Later a friend showed me Modula 2 and I was instantly in love with that language.

Real programming then in school (C, C++, µC assembler).

...another (probably about fourth) completely futile attempt at making MASM compiling pipeline work...

...what the fuck... seriously, i've spent together about two weeks of time trying to make a fucking default hello world compile... ml64 problems, then rc.exe problems, apparently i was missing some dumb CommonService.dll which not only doesn't exist anywhere on my computer, but it doesn't even seem to exist at all in this fucking dimension. After several hours I had the bright idea of "fuck MS rc, let's just grab any other random resource compiler that I can find, and see if that one works".

Funnily enough, it does. Except Visual MASM can't run it from it's build process because it fucks up the commandline call, so I need to run it manually, and then when I run the build from V-MASM, the rc call still fails, but then it checks for the resulting .res file and finds it, so it happily continues with success...

...and now fuckin... what even is it? *goes to check*
oh yeah, now linker is shitting itself:
LINK : fatal error LNK1104: cannot open file 'user32.lib'

And I'm just completely defeated, just searching system-wide for the lib intending to copy it into the linker folder because fuck this fucking bullshit, I've had enough of drowning in MS BuildTools versions and installations and uninstallations and fixes and modifys and repairs and all that FUCKING BULLSHIT.

HOW. THE. FUCK. is this in any way usable for anyone. I suspect nobody ever actually tried to build an assembler project in the last 30 years, so nobody noticed it DOESN'T. FUCKING. WORK.

THIS.
THIS is why I hate anything that's not a proper IDE where I install ONE thing, and do everything in that ONE IDE and let IT figure out all this linuxy-soft-coupled bullshit of twentyfuckingthousand fucking useless commandline apps threwn around the whole fucking system where I'm fucking supposed to know where the fuck what is and which version and GO FUCK YOURSELF.

GIMME. FUCKIN. ONE: IDE. WHICH. WILL. INSTALL. ALL. THAT. IT. NEEDS. TO. BE. FUCKING. ABLE. TO. FUCKING. WORK. AND. COMPILE. SHIT!!!

FUUUUUUUUUUUUUUUUUUUUUUUUUUCK.

Everytime I see 76 I think HALT.

Best: VSCode, Typescript, Webpack
Worst: mov ax, bl

what do you recommend for me to learn about next?
I have learnt about:
- web frontend/backend (php)
- android and java
- c, c++, nasm, gnu assembler
- parallel computing
- cli operating systems

with that background, what would you recommend?
I'm considering:
- neural networks
- making a server
- ethical hacking
- starting a blog

worst dev tech ever for me was intel x86 assembler. I developed on motorola 68k before and i loved it. x86 was horror.

start learning assembler

Shit bathed and stack smashing ass loads of fuck.

I wrote a virtual machine, and just to fuck myself harder, I make the decision of applying some fancy dumbass theories of mine. This translates to a piece of shit modular design that works exactly as intended, but constantly gives me vietnam flashbacks to the horrifying, multiple concurrent instances of my younger mind being incessantly turbo-raped by the dozen object-obsessed pedophiles that I initially studied under.

Now, were they *actual* pedophiles? No, of course not. But I have to make fun of the acronym somehow and that's what came to mind, leaking horse dung all over the walls, floor, curtains and carpets.

Anyway, I feel so smart after this traumatic experience I just have to keep doing it to relive the terror once again. Find me in the corner, laying down in the fetal position, sobbing until the tears build up and drown me in this well of despair, or rather this finely shit painted portrait of a toilet in a lonely and stinking unisex public bathroom stall.

But let me squeeze these fucking tits a little bit harder, because that's my actual day job. That's right. I get PAID for slapping around mammary glands, it's not much but it's an honest living.

So where was I? Ah, yes, absolute degeneration. I'm truly the Max Wright of programming, mostly for smoking crack and having unprotected sex with homeless people, but also for keeping alien life forms in my basement that go out at night to hunt for sweet feline delight.

But as I keep going, I decide I want a language for the machine so I don't have to punch bits by hand all fucking day like an idiot, so alright let's make a small assembler for this shit... oh, right, except it's not small, because gently suckle the bile out the lips of my fucking butthole.

I may redefine a load of shit two months down the line, so I have to make everything perfectly encapsulated and easily fucked with -- which in my licking vomit off the floor of a porn theater travesty of a case means I'm generating half the code and scrambling as hard as I can to glue everything together.

Does it work? Of course it works, I'm Max Wright bitch. I can redefine the ISA all I want, anytime I want without breaking anything because of my pristine crackhead encapsulation. And to credit the scrambled eggs I have for fucking brains, it's not even *that* complex.

The problem is I keep forgetting shit, not how it works, just that it's there. So I forget that I have a virtual machine, and I forget that I have an assembler, and so I spend an entire day trying to figure out how the fuck I'm going to handle a loop inside an unrelated interpreter.

By the time I manage to remind the drooling undead jackass that is this husk that my irredeemably demonic self inhabits, that we can easily solve this by using the tools we've already built, it's so late and we're so tired there's not much we can do. All this time, WASTED.

Which circles back to crack. Are you tired of blowing your babysitter for cash? Have you considered suicide by a thousand used trojan condoms? Is your roommate possesed by the forces of Avernum, and now seeking all-destructive vengeance against your rectum?

Try no other than Soul Excision, the treatment that will neuter your being and curse it to the TRUEST form of eternal damnation! Through Soul Excision, you will be CUT OFF from the very essence of the universe, and turned into an astral prostitute that offers their EVERY orifice to the BUTTLOADS of maggots that debour their mind and body, all for the pleasure of some rich and powerful wankers that *deeply* enjoy watching questionable erotic tapes from nightmarish outer dimensions!

Use my promo code SLUTSKANK for 20% OFF in your very LAST purchase on this earth! And once you surrender your BODILY holes to cosmic oblivion, remember: when it comes to your ASS, we're ALWAYS open for business!

Thanks to Soul Excision for sponsoring this DDDDDDDDDDDDDDDDDDDDD$$$$$"2402"$$?"="$0"?¿"=¿?40'0"$="¿¿=$¿"?=4¿?"$="?¿$="¿?$0¿?"=$¡'0$"¿?$=::::::

:~%

I told you guys that I would update you on my PiBM-5150 project. I figured out the hard way that my USB to DB-25 cable wouldn't cut it. Seems it is for printers and no matter how hard I tried it wouldn't work because of the path of the wires. After researching, it is apparent that the GPIO pins on the pi are configured for serial by default but it requires a little voltage change from TTY to RS-232. Rather than do like one of the videos I saw and solder junk to a bread board, I found a serial (rs-232) shield and 9pin output for the pi. Now, both computers are true rs-232 each. Instead of using a modem between them, I bought a null modem cable (crossover of Tx Rx signals) to interface the two machines directly. I'll update this evening to show it hopefully working.

My first exposure to computers was the TRS-80 (a.k.a. TRASH-80) my mom (the city Library Director) bought for library patrons to use. It’s data store was on a cassette tape and programs came on cartridges, IIRC.

Around the same time I was learning to do Logo and BASIC on an Apple IIe in 5th grade.

My cousin’s Commodore 64 came next and my grandma saw how my interest in computers was blooming, so she suggested I use the savings I had built up from birthday money and mowing lawns to buy an IBM PC/AT 8088 clone. $1,300 later and lots of time in my basement figuring out how to build it all from separately-shipped components, I was on my way to learning Assembler, BASIC, and DOS.

What's the strangest Assembler or Pseudo-Assembler you've ever encountered?

I wrote a Z-machine (Infocom's virtual text adventure interpreter) and it was quite an interesting interpretation of bytes:
- The first 3 bits of an instruction tell you the opcode category, the rest are the instruction
- The 2nd (and maybe 3rd) byte tell you in 2-Bit chunks the operand types.
- text is encoded in 5-Bit chunks, with special characters for CapsLock that double function as padding (if your text doesn't align with the 3 letters per 2 bytes).
- and of course there are 5 different versions that all work slightly differently (as in CapsLock becomes Shift or "this special character isn't in use anymore")

wire hell - > assembler hell -> DLL hell - > npm/nuget hell

History repeats itself.

Picking up girls

Me: We will be like C and Assembler.
Girl: Why?!
Me: Cuz I will decompile into you... ;)

Why all these SW engineer interviews include 2 days of questions about sophisticated algorithms which i have never (and probably will never) have chance to even reuse, because they are NOT simple & understandable for any project community? IMO It is like asking to show Assembler skills on frontend-dev interview...

Out of the frying pan, into the fire:
So in my first job, I thought it's just us operating so crazy: meddling with arcane C/C++ code from the 80's, shooting our code to production without testing, fixing hundred of customers data base entries by hand, letting an intern alter some core component (to have more logging) and directly push it to prod...
Silly me.
I mean I suspected, that maybe it's not only this tiny little company acting wild, that also the bigger companies with all their ISO certified processes, agile blabla, professional tooling whatsoever - will also have their skeleton in the closet,.. like some obscure assembler part buried in the heart of your code base nobody dares to touch...
How Pieter Hintjens asked about the state of the industry and all the fads so bluntly put it:
"It's all bullshit."
But we are humans, so we better jump on the bandwagon if we want to keep our jobs... and somehow try to keep that trashy house of cards from crashing down.

ATTENTION PLEASE! Important announcement following:

Please check your interface implementations for correct byteorder according specification BEFORE YOU START COMPLAINING ABOUT DATA FAILURES ON EXCHANGING DATA.

Freakin hell, if I'd get some money for every byte order mismatch on testing interfaces, I'd be a be a billionaire.

And why are all those highlevel I-know-every-fucking-framework developer incapable of checking the real memory content of a datatype, and the real data content on the interface even if you tell them that their byte order is obviously wrong?
No, your system is not the centre of the universe and I don't care how you get your less-than-32bit-datatypes-are-for-assembler-usage-frameworks to change byteorder. It's not rocket science, if there's no ready-to-use-function then write those 4 lines yourself.

Next time I get to specify an interface I'll go for mixed-endian, just to make sure everybody involved knows the concepts of endianess afterwards.

TL;DR: Computers and I go way back, but I don't know how I ended up as a dev - and am still not certain that's what I want to do for the rest of my life.

Rewind to the early 80's. My friends at the time got the Comodore 64 one after the other. I never got one. Heck, we didn't even have a color TV back then. Only a 12/14" small B&W TV. It's easy to conclude that I spent a lot of time at my friends'.

Back then it mostly was about the games. And, living in the rural countryside, the only way to aquire games was to pirate them. Pirating was big. Cassette tape swapping and floppy disk swapping was a big deal, and gamers contacted eachother via classifieds sections in newspapers and magazines. It was crazy.

Anyways. The thing about pirated games back then is that they often got a cracktro, trainer, intro or whatever you want to call them - made by the people who pirated the game. And I found them awesome. Sinus scrollers, 3D text, cool SID-tunes and whatnot. I was hooked.

My best friend and I eventually got tired of just gaming. We found Shoot'Em-Up Construction Kit, which was an easy point-and-click way to create our first little game. We looked into BASIC a bit. And we found a book at the library about C64 programming. It contained source code to create your own assembler, so we started on that. I never completed it, but my friend did.

Fast forward through some epic failure using an Amstrad CPC, an old 486 and hello mid 90's. My first Pentium, my first modem and hello Internet! I instantly fell in love with the Internet and the web. I was still in school, and had planned to enter the creative advertising business. Little did I know about the impact the web would have on the world.

I coded web pages for fun for some years. My first job was as a multimedia designer, and I eventually had to learn Lingo (Macromedia Director, anyone?) And Actionscript.

Now I haven't touched Flash for about 7 years. My experience has evolved back to pure web development. I'm not sure if that's where I will be in the future. I've learned that I certainly don't know how to do everything I want to do - but I have aquired the mindset to identify the tasks and find solutions to the problem.

I never had any affiliation with the pirate scene or the demo scene. But I still get a little tingling whenever I see one of those sinus scrollers.

Tech-Report has a section featuring mov instead of move.
Spot the assembly coder ;D

My first dev project was back in the 80's. I might have been around 10, I think.

My friend and I had been tinkering around Shoot'em up construction kit for a while, plus we'd been quite inspired by all the cracktros, intros and whatnot was popular back then (piracy was huge, at least on the C64 platform - I don't think I ever saw an original game until my parents bought an Amstrad CPC).

Anyway, we were inspired. We didn't know how to code except some basic BASIC (ba-dum-tsj). We borrowed a book from the library on how to code an assembler for the C64 in BASIC, and coded for days. I eventually lost interest, but my buddy did actually complete it.

It’s all a blur but in 5th grade I was using a TRS-80 with a cassette player for storage at the library where my mom worked. Also an Apple IIe at school in the computer lab. My first personal computer was an IBM XT clone with an 8086 processor and dot matrix printer. I bought it after having fun with my cousin’s Commodore 64 and wanting one, but his uncle sold me on the IBM platform as something that I could upgrade over time. I was 13 when I first learned Assembler and BASIC. Big Blue Disk was my favorite subscription software with all the games and other shareware stuff that came every month in the mail.

As @shoop said, learn to Google is essential. Also, if the interest isn't on top, mentor them, give them tasks that build on each other. And don't start with assembler language.

(heading)How a programming language is created? Because I want to make my own.(heading)

I am learning C and next I will learn C++, SQL,DS&A, Assembley, Lex&Yacc,Operating Systems, Computer Arcticture, Computer Networks because I think it's enough for my goal. The only reason I am learning this, to make my own C++ clone with my own knowledge. But I really don't know how can I create my own programming language like C++ from scratch. Like what are the first steps to began with. As I know that C, first step is Preprocessor then Compiler then Assembler then (Loader/Linker).

Anyone please give me a step by step guide like learn this language first then this then this. So I can finally reach that amount of knowledge which I can implement to create my own programming language like C++.

The rear ducking continues. We've built a reliable translator in the dumbest fucking way possible, it's just lovely. I simply reused the structure for feeding data to the VM assembler, an array of arrays, where there's one array of (ins [args]) per node in the parse tree.

It's nice because nodes can be solved out of order without affecting the actual sequence in which the instructions are output. And if one statement (node) equals multiple instructions, you just push multiple entries to the corresponding array, or push nothing if you need to output nothing. Easy as goblin pie.

This is enough to convert an input language to the assembly-like intermediate representation we use for the virtual machine. So then there's doing it backwards: walk the same array of arrays, and map those virtual instructions to a physical architechture. I guess I could do the encoding to native binary myself, it'd certainly be interesting to try, but I'm burnt-out already so I'll just use fasm for now.

Initial test: wrote a test program in my own stupid language, ran the translator, dump output to file, assemble that with fasm, run with r2 -d.

Crashes? No.
Runs fine? Yes and no.

For fuck's sake, I don't have syscalls. Mainly because the VM doesn't have an operating system, lmao. I was testing virtual programs by just freezing state, terminating, then dumping the fucking registers and stack to the console, we have no I/O to speak of. Not even a real 'exit', VM handles that by reading a return value every step like a mentally damaged son of a bitch.

So anyway, I manually paste the linux mambo, you know:

mov rax,60
mov rdi,0
syscall

And NOW our program can end execution without crashing.
Okay then, so does the test code work correctly?

** DRUM ROLL **

Yes.

Ladies and gentlemen, mother fucking PESO is now a compiled language, and going forward I will be expectantly receiving your marriage proposals for reviewing. Oh, but not so fast, we still need a frontend...

Well, we'll handle that in the next few days. I'm just glad to be *nearly* finished with this fucking compiler, I want nothing to do with anything else ever, but we know that's not going to happen, so Lord please end my pain.

No sponsor as this rant has been paid for by tax evasion.

Okay, so most of the backend stuff is done: the parser, VM and assembler can be considered in working state. Now I only need to combine these bytecode files I'm outputting to enable including and-- FUCK. I HAVE TO WRITE A LINKER.

Imagine you are hired to teach assembler to an amoeba and they pay you well... Lol lol

Started to learn assembler.

On Windows.

10.

Rubber ducking your ass in a way, I figure things out as I rant and have to explain my reasoning or lack thereof every other sentence.

So lettuce harvest some more: I did not finish the linker as I initially planned, because I found a dumber way to solve the problem. I'm storing programs as bytecode chunks broken up into segment trees, and this is how we get namespaces, as each segment and value is labeled -- you can very well think of it as a file structure.

Each file proper, that is, every path you pass to the compiler, has it's own segment tree that results from breaking down the code within. We call this a clan, because it's a family of data, structures and procedures. It's a bit stupid not to call it "class", but that would imply each file can have only one class, which is generally good style but still technically not the case, hence the deliberate use of another word.

Anyway, because every clan is already represented as a tree, we can easily have two or more coexist by just parenting them as-is to a common root, enabling the fetching of symbols from one clan to another. We then perform a cannonical walk of the unified tree, push instructions to an assembly queue, and flatten the segmented memory into a single pool onto which we write the assembler's output.

I didn't think this would work, but it does. So how?

The assembly queue uses a highly sophisticated crackhead abstraction of the CVYC clan, or said plainly, clairvoyant code of the "fucked if I thought this would be simple" family. Fundamentally, every element in the queue is -- recursively -- either a fixed value or a function pointer plus arguments. So every instruction takes the form (ins (arg[0],arg[N])) where the instruction and the arguments may themselves be either fixed or indirect fetches that must be solved but in the ~ F U T U R E ~

Thusly, the assembler must be made aware of the fact that it's wearing sunglasses indoors and high on cocaine, so that these pointers -- and the accompanying arguments -- can be solved. However, your hemorroids are great, and sitting may be painful for long, hard times to come, because to even try and do this kind of John Connor solving pinky promises that loop on themselves is slowly reducing my sanity.

But minor time travel paradoxes aside, this allows for all existing symbols to be fetched at the time of assembly no matter where exactly in memory they reside; even if the namespace is mutated, and so the symbol duplicated, we can still modify the original symbol at the time of duplication to re-route fetchers to it's new location. And so the madness begins.

Effectively, our code can see the future, and it is not pleased with your test results. But enough about you being a disappointment to an equally misconstructed institution -- we are vermin of science, now stand still while I smack you with this Bible.

But seriously now, what I'm trying to say is that linking is not required as a separate step as a result of all this unintelligible fuckery; all the information required to access a file is the segment tree itself, so linking is appending trees to a new root, and a tree written to disk is essentially a linkable object file.

Mission accomplished... ? Perhaps.

This very much closes the chapter on *virtual* programs, that is, anything running on the VM. We're still lacking translation to native code, and that's an entirely different topic. Luckily, the language is pretty fucking close to assembler, so the translation may actually not be all that complicated.

But that is a story for another day, kids.
And now, a word from our sponsor:

<ad> Whoa, hold on there, crystal ball. It's clear to any tzaddiq that only prophets can prophecise, but if you are but a lowly goblinoid emperor of rectal pleasure, the simple truths can become very hard to grasp. How can one manage non-intertwining affairs in their professional and private lives while ALSO compulsively juggling nuts?

Enter: Testament, the gapp that will take your gonad-swallowing virtue to the next level. Ever felt like sucking on a hairy ballsack during office hours? We got you covered. With our state of the art cognitive implants, tracking devices and macumbeiras, you will be able to RIP your way into ultimate scrotolingual pleasure in no time!

Utilizing a highly elaborated process that combines illegal substances with the most forbidden schools of blood magic, we are able to [EXTREMELY CENSORED HERETICAL CONTENT] inside of your MATER with pinpoint accuracy! You shall be reformed in a parallel plane of existence, void of all that was your very being, just to suck on nads!

Just insert the ritual blade into your own testicles and let the spectral dance begin. Try Testament TODAY and use my promo code FIRSTBORNSFIRSTNUT for 20% OFF in your purchase of eternal damnation. Big ups to Testament for sponsoring DEEZ rant.

Couldn't figure out why I had to make so many cats meow to learn how to program. I wanted to move things on the screen and create sounds. Then, dug up an old c64 and programmed myself a monitor and got into assembler which was a breeze compared to programming dumb text outputting felines.
After learning computers from the ground up, I started realizing that C++, C#, Java etc. actually wasn't at all about constructing and deconstructing cats or its base class animal.
I had one final go and it all just clicked!

Problem: in assembler, i want to proceed an string byte by byte. How can i do this?

My try:

Mov ebx, 0
S:
Mov eax, [var +ebx]
;somethin
Add ebx, 1
Jmp s

But it doesnt cut off the thing rigth

At some point I need to do an older project i've had on hold a while, but it'd require writing my own ROM patch system as a major step in completing it, as i'd need to dynamically patch stuff into older games based on system, which current patch formats don't allow for. (This project will also help me learn a few things I need for yet more projects I've got stashed away, so it needs to happen eventually.)

Now, the interesting part: the patch format. I was debating on whether to use binary data, like IPS/BPS and similar formats do, which would be easier to implement... but if I were to have plaintext patches, you'd be able to not only understand what's happening, but also have things like scripting and conditionals and user-defined options and such. This would be WAY harder to implement, slow as fuck, and require an assembler per-target-system, either external or internal... but it'd be transparent, editable, and hella extendable.

This would all happen after I'm both over my burnout AND done chewing through my current stack of projects and such, of course, but still... which sounds better to you, dear reader?

Not being suitable for eveything is my biggest annoyance with Python. Give me Python with the performance of assembler and I'll be in heaven :)

A compiler and assembler set for bootstrapping the whole gcc Code tree and cross compiling each level

I think I was around the age of 11, and got a brand new C64 with 1541 floppy. The manual of the included floppy disc with some programs described the program startup with 'load "name",8,1'
So I typed (exactly that) 'load "name",8,1' and got '?FILE NOT FOUND ERROR', did it again, same error.

After half an hour of reading the manual and trying it several times, I gave up and went to a friend with a C64. I told him the disc doesn't work, if he could help me out.

He put the floppy disc in and typed 'load "frogger",8,1' and seeing the command I realized what a tremendous idiot I was.
Surely it worked, he could play frogger.

Went home desperate and broken with my disc and from that day on I could operate that machine.
I soon started to play around with basic and a bit of assembler.

Best: the U2 pilot's handbook, as you _wanted_ to read it.
The S370 assembler docs. Everything you needed and nothing more.

Worst: where to start? How about the defect reports produced by contemporary QAs? Maybe a screenshot, and an implied demand for telepathy. Mate, you're a mindless drone, the definition of brainless. Applying telepathy on you is pointless.