Hey Now!

Hey now!

Kotlin is a wonderful language!

For example, when exiting a coroutine, Kotlin AUTOMATICALLY throws a specific exeption and automatically catches it, to show that the coroutine exited normally.

Now, you may think it is bad to use exeptions as part of normal programming flow, but it is NESSESARY to re-invent GOTO's in a high level langauge like Kotlin!

/s

this year i'm in the mobile development trenches and it feels like it just gets worse every time i get back into it. if i never have to hear the words "gradle" or "kotlin" again i would be very happy. whatever those even are

And we sometimes forget that we create those limitations. For example, nearly all robots with cameras use red, green and blue sensors...

Despite... they don't have to

every single thing involving a computer is designed to put something into our senses. until a human looks at it, and interprets it, it is nothing. it isn't 'data'. it isn't 'ones and zeroes'. it's just some electrons and photons moving around, as is their wont.

but if we arrange those electrons just so, and let them do their thing, we can create a pattern that someone will experience as bits, registers, numbers, letters, instructions, algorithms, messages, financial transactions, videos, thoughts, worlds, etc etc.

the whole project of computer programming is corraling the electrons into situations where they will obey rules we have in our heads. electrons are surprisingly predictable, so this isn't a fool's errand. but every layer of the stack of abstractions is something we built: arranging one thing to produce a pattern we want to see. the chip arranged so the 'high and low voltages' fit our idea of 'bits' and 'logic gates'. the screen whose lights create a 'field of colour' for an organism that has this level of visual acuity, this frequency response in its cone cells, this capacity to see shapes and edges. these bits and logic organised into an 'algorithm' that takes 'data' that we think of as 'vertices' and 'triangles' and produces the appearance of 'perspective rendering', which approximates our concept of a '3D object', of even a 'virtual world'.

we have gotten so very very good at producing these patterns that it's easy to see them as something natural, and miss all the layers of orchestration behind even the simplest operation. computers are a game played between humans.

It is a cheap attack on nonmonogamy. I have also heard "ethical polyamory. When I asked what the heck that was, I was told "polyamory but where everyone involved is consenting and in the know".

Basically the idea being made is:

Monogamy is ethical, normal and good by default.

But non monogamy is corrupting, unethical and destructive by default. So you MUST specify that the one you are talking about is ethical. Because he default is unethical.

In short, it is bullshit

The term "ethical nonmonogamy" confuses me. Like is that just a weird way of saying polyamory/dating but not having sex monogamously or is it something else and I'm totally off base?

Honestly, how I learned was via make.

Like... you can easily find compleatly incomprehensible make files that automate everything.

Those you can use, but they are not how you learn.

How you learn iz by doing it very very copy-paste of the lines toh would write to the compiler in a shell. Most basic one with a single .c file would be:

gcc main.c

Then figure out what arguments to add to it to make it how you want. Name the output file. Have the source file in a different folder. Have the ouput be in a different folder.

You now know how to compile a single file by using a shell

Now. Create a make file. Simply have it call exactly the same thing you wrote in the shell before.

Then figure out how to compile a main file and a file with functions and a header. Again, first just by using a shell. And then build it into your build file.

This is not too hard. There are plenty of guides and examples. It is fun exploration where you get your hand dirty and you will learn a LOT about how coding projects and IDEs work.

A programming IDE is just a text editor and make file builder with a pretty GUI on top

It is not magic. And it is not even that complicated.

Sure. Automating it and making it solid and taking all the things that may change into account so it can be generic is hard

But creating a make file that will compile YOUR project? Not hat bad.

never learning how to properly handle multi file c projects is finally catching up to me and stabbing me to death with linker errors.

I hope it all works out for you!

I hope you find answers to all your trouble and your workflow gets smoother!

I hope you find cheatsheets to help you and manage to write notes that helps you remember!

bitch java is so fucking annoying why does the S in String need to be capitalized but the i in int has to be in lowercase??? why do you need to import a whole ass module just to take an input from the user??? why are all the commands so fucking long and hard to remember??? JUST DIE

Yep. At least not taken seriously by normies. But this is why I have partners! :D

95% of my emails for work is written in the evning.

When I can get my partner to help me.

I am VERY good at cooding, system design and the politics to get good design accepted.

I am very bad at anything that involves "Just do it normally". I do not know what it means

Social rules, writing emails or accepting invitations... anything like that

Too mentally ill to be “normal,” too good at faking functionality for people to take my issues seriously.