Don't understand USB storage?
Well here it is, in a nutshell -

Stack Overflow users in a nutshell:

*8 months ago*

Noob: "How can I do this with Javascript?"
SO User: "You should use jQuery. Here's how to do this in jQuery."

*Now*

Noob: "How can I do this with jQuery?"
SO User: "jQuery is redundant now. Here's how you can do it with Javascript."

The process of piecing it all together in a nutshell.

>>> print(whoSaid("OlderFriend"))
About 20ish years ago I was working in IT, and it was about around this time where CD-Roms were hitting the stores and becoming the newest craze. However, Microsoft did not write the drivers correctly for this new hardware.

In a nutshell, the driver would be installed and the user would lose the sound to their speaker.

How did this happen? By altering the way the interrupts worked on the computer. At the time there only existed a few unreserved IRQs or Interrupt ReQuests. The installer package would redirect IRQ 5 which is "User Selectable (Sound Cards)" to work with the CD-Rom. This was fine and all unless you wanted to listen to your speakers.

I had come up with a clever hack through rewriting a config file that would be run during bootup. So at the time of boot up IRQ 5 would be dedicated to the sound card, and IRQ7 (which was usually for the Lpt1 Printer) would be dedicated to the CD-Rom. This worked.
And because I was IT at the time, I would get a lot of calls for fixing this problem.

So, as you can imagine, I've gotten **really** good at doing this. I didn't even need to be at a computer to walk someone through the problem.

I receive a call one day, it was a problem with the CD-Rom and sound card. I walk him through the problem and he reboots his computer. I could hear him on the other side jumping with joy when he was able to put in his music CD and hear sound coming from the speakers.

He asks me, how in the hell did you figure this out!? You're a fucking Genius!

And I said, It's not rocket science it's just a computer.

There was a long pause of silence.

Uhhh... Hello? Did I say something wrong?

Sir, I work at NASA I deal with Rocket Science on a daily basis.

Recruiters and devs in a nutshell

Q: Your resume says you're fast at solving math problems?!
A: Yes
Q: What's 214x21?
A: 3249
Q: But, that's not correct!?
A: Yes, but it was fast!

Notepad: Check
Tea: Check
Stack Overflow: Check
Devrant Stressbal: Check

Let's get productive!

*Moves to another town to start a new job
*Been living in a dorm for the past month
*Starts looking for flats to rent
*Misses a few nice ones because he finds their ads a few hours late
*Starts developing an app that looks for new flat ads that matches his requirements and notifies him of their existence
*Finds a nice flat by accident before he even finish developing the app
*Refuses to rent it only because he believes his app could do better!

Me in a nutshell!

My life in a nutshell.

I've been stuck in this timeless loop for 10 years, anyone that relates?

1. Set alarm before going to bed.
2. Alarm rings, I turn it off.
3. Wakes up late.
4. Work from 08 AM to 4 PM.
5. Take the train back home
6. Plan what to do for the rest of the day.
7. Come home, do everything except what was initially planned.
8. Watching time goes by while doing non-productive things.
9. I feel alone, watch porn to fill this void.
10. I get depressed and unhappy afterward
11. Set the alarm for the next day.
12. Repeat.

!rant
Observed a full deployment the other day and discovered it's extremely inefficient. I proposed an idea to fix it, and was shot down by a senior dev on the team. I was ranting about how asinine the process was and how my process could reduce the amount of time and training required to do deployments with out any additional cost or overhead. A senior dev from another department over heard me, found my workspace and told me (in a nutshell), "write up a document about why the current process is garbage and how yours is better, and how it works, I'll review it and we'll get it worded and formatted right. When we finish the document, I'll forward it to the CTO of your department with your name on it and my recommendation for review." Fuck yeah. 😈😎

If there's anything I've learned till now then that's: You should know how to Google the *RIGHT* thing

Things I haven't learned: How to Google the *RIGHT* thing

HTML Previewer: "Yeah it looks fine"

Chrome: "no your HTML fucking sucks, go back to coding school"

WYSIWYG in a nutshell

I just lost faith in the entire management team of the company I'm working for.

Context: A mid sized company with
- a software engineering departmant consisting of several teams working on a variety of products and projects.
- a project management department with a bunch of project managers that mostly don't know shit about software development or technical details of the products created by engineering.

Project management is unhappy about the fact that software engineering practically never sticks to the plan regarding cost, time and function that was made at the very beginning of the project. Oh really? Since when does waterfall project management work well? As such they worked out a great idea how to improve the situation: They're going to implement *Shopfloor Management*!

Ever heared about Shopfloor Management? Probably not, because it is meant for improving repetitive workflows like assembly line work. In a nutshell it works by collecting key figures, detecting deviation in these numbers and performing targeted optimization of identified problem areas. Of course, there is more to Shopfloor Management, but that refers largely to the way the process just described is to be carried out (using visualisation boards, treating the employee well, let them solve the actual problem instead of management, and so on...). In any case, this process is not useful for highly complex and hard-to-predict workflows like software development.

That's like trying to improve a book author's output by measuring lines of text per day and fixing deviations in observed numbers with a wrench.

Why the hell don't they simply implement something proven like Scrum? Probably because they're affraid of losing control, affraid of self managed employees, affraid of the day everybody realizes that certain management layers are useless overhead that don't help in generating value but only bloat.

Fun times ahead!

StackOverflow in a nutshell
This gets me so angry; Two identical answers, one downvoted into oblivion and the other one upvoted like it is a holy grail.

C++ errors in a nutshell

(The pics is from my college computer lab where it takes us forever to get a proper output )

(Maybe it's we who suck) xD

I feel like I need to clarify the concept of toxic masculinity and toxic femininity.

The masculinity itself is not toxic! Being a masculine man is not being toxic. Being a man is not being toxic.

Toxic masculinity, in a nutshell, is:
- Teaching boys to never express their feelings. Men don't cry. You should always maintain the “tough” image. If you open up about how you feel, you're a pussy. Domestic abuse of men doesn't exist. A man can't be raped by a woman.
- You should only depend on yourself. Even if you're in trouble (say, with depression or bullying), and you ask for help, you're a pussy.
- Boys will be boys. Aggression is typical for men, and expressing it beating other men is a manly behaviour.

There is also toxic femininity:
- Men should work and provide for the women. Women shouldn't work, they should instead be housekeeping and raising kids.
- Women should be pretty and work on their looks (to attract men).
- If you don't have kids by the age of 30, there is something wrong with you.

It almost seems like traditional grotesque gender roles diminish the personality for the sake of social conformity. The pattern is always “men should”, “women should”. They tell you what to do, authoritatively so, based on your biological sex. They try to “put you in your place” where you “belong” just because of your genitals. This is toxic.

It is important to retain personality. The ultimate goal is to get rid of those stereotypes and finally throw them in the garbage bin where they belong. Because of them, we have anorexia in women (the most deadly mental disorder), and also male suicides through the roof.

Before you label me “feminist”, bear in mind that the third wave is all over the place, to the point they can't agree on what feminism is.

Separation of concerns is a beautiful thing.

JSX is fucking ugly. Fuck that shit. I hate JSX with a passion.

Here is one. Did you know that the digestive system works really hard to digest the food eaten?

How about we blend all the food before consuming it? Take a blender and add a cup of coffee, add some salad, add a piece of cake, a few slices of pizza, hot sauce and for good measure add some juice, or whatever-you-eat-for-lunch.

After all, all that food is going to get mixed anyway. This is more efficient!

No? Why not? Because it's ugly, highly unappetizing, disgusting even, and it takes away the pleasure of eating, the enjoyment of a good meal.

That in a nutshell is JSX: mashing up everything together under the pretext of efficiency.

Web development not only is an art, but above all must be enjoyable to those who devote their lives to it. And ugly ain't gonna cut it.

I've spent a lot of time messing around with C, having struggled with object-oriented programming (due to not really knowing how best to structure things, not knowing when to apply certain design patterns).

When writing C code, I'd write OOP-esque code (pass around a struct to routines to do things with it) and enjoyed just making things happen without having to think too much about the overall design. But then I'd crave being able to use namespaces, and think about how the code would be tidier if I used exceptions instead of having every routine return an error code...

Working with Python and Node over the past couple of years has allowed me to easily get into OOP (no separate declaration/definition, loose typing etc.) and from that I've made some fairly good design decisions. I'd implemented a few design patterns without even realising which patterns they were - later reading up on them and thinking "hey, that's what I used earlier!"

I've also had a bit of an obsession with small executable files - using templates and other features of C++ add some bloat (on Windows at least) compared to C. There were other gripes I had with C++, mostly to do with making things modular (dynamic linking etc.) but really it's irrelevant/unreasonable.

And yes, for someone who doesn't like code bloat, working with Node is somewhat ironic... (hello, node_modules...)

So today I decided to revisit C++ and dust off my old copy of C++ in a Nutshell, and try to see if I could write some code to do things that I struggled with before. One nice thing is that this book was printed in 2003, yet all of its content is still relevant. Of course, there are newer C++ standards, but I can happily just hack away and avoid using anything that has been deprecated.

One thing I've always avoided is dynamic_cast because every time I read about it, I read that "it's slow". So I just tried to work around it when really if it's the right tool for the job, I might as well use it... It's really useful!

Anyway, now I've typed all this positivity about C++ I will probably find a little later on that I hit a wall with what I'm doing and give up again... :p

!Dev related but still freelance.

So.. I do 3D stuff, scenes, animation and so on. The e-sport pub manager I know told me about this guy that wanted to start a local organizations around FIFA, hold tournaments at the pub and so on. He had some finance, contacts and needed a 3D scene of a stadium to highlight top placers as 3D Fifa cards.

Gotcha, so I hooked him up with said stuff, he was happy, manager was happy, first tournament went well. Now to the shit show:

He wrote to me a couple of days later asking if I'm up for more jobs, which k respectfully declined because l was on a bigger project that took about 2months to complete. Since that day, he spammed both me and the pub manager with request and wishes on wanting to do more.. and I mean SPAM!

Like the dude can't take a no, sorry. He tried to call on phone and messenger, messeged me several times / week and asked the manager of he heard from me.

Both the manager and I were perplexed of his attitude and after asking several times to stop and we both had other things for now (events / projects).. he.. he didn't stop. So.. blocked and that's that, right? Fuck now.. other clients of mine asked me if I knew of him because he tried to contact them to get to me.. like WTF?! How hard is it to take a no and move on?! Jesus.. client of hell in a nutshell

Imagine you have a car and it runs faster than other cars and needs less gasoline, but due to historical reasons the steering wheel is made of barbed wire, there's 8 different accelerator pedals for different streets, pushing the wrong one may lead to a crash, and instead of a driver's seat there's a huge wooden dildo sticking out of the floor.

This is, in a nutshell, what using the C++ type system feels like.

My first software.. Okay. So first time I ever attempted was with my father, i was around 8 or so, i remember very little from it, but in nutshell, i somehow ended up at his job having day off school or something, no idea.

Apparently he was bored, so he decided yo show me... Basic. Yep, thats right. Frking basic. Anyway, he shown me some really basic stuff in basic, and pushed the envelope really hard, just trying to force into me more and more in these 8hrs. I started with filling screen with "o" characters. Most of times he was telling me what to write with elaborate explanation why. At the end of the day, we finished with simple maze game where player was "o" and maze walls was #. Without any goal, or anything.

Next day i was at point 0, understood nothing from it except how to handle keystrokes (and belive me, that for me was huge mindblow, and even bigger mindblow that it actually made prefect sense).

I dont remember much, but later i started with father-assisted c++ and some pascal. I immidietly loved c++ but dropped learning it for (NullPointer) reason.

Thats not really project imho, so now time for my actual first project.

It was about time when ARK survival evolved was a fresh thing, i was playing it a lot. Server admin became buddy. We all complained about max level cap, but to change it in config you needed to input whole new xp curve.

At that time i had great familiarity with google and computers, some thought i was some kind of PC god (seriously I heard someone saying so about me lol) just becouse I could ressurect most cases of broken windows. And I had next to zero programming expirience. It was about to change. I made first c++ actual program, that was making xp curve for you. It took me just bearly 2 days and was series of cin, cout, one file open, some maths in loop, and done. Maths was very bad. But i pushed it into steam forums, and one guy responded how.bad my math was, so we colabed on making 2 iteration. Took around week. Than half a year passed and we wanted go big. Go gui. I had no freaking idea how making gui looks like. Community liked my cli tool, we had quite a lot of downloads, why not go GUI. And thats when I discovered QT framework. And we had few features in mind... It took us half a year to make it. From 60 lines of code i jumped into 1k lines of code. We pushed it and immidietly started working on 4th version with much greater customizability etc.

Than i finished 18 and found a job. Job in php. I got it becouse I made this project.

Now project is abandon. This project also gave me a lesson that donations will not feed you.

Edit: and before you think about my father that he was nice person to show me code, trust me, i dont know bigger dick than him.

My friend sent me this as WYSIWYG

/* A simple quine (self-printing program), in standard C. */ /* Note: in designing this quine, we have tried to make the code clear * and readable, not concise and obscure as many quines are, so that * the general principle can be made clear at the expense of length. * In a nutshell: use the same data structure (called "progdata" * below) to output the program code (which it represents) and its own * textual representation. */ #include <stdio.h> void quote(const char *s) /* This function takes a character string s and prints the * textual representation of s as it might appear formatted * in C code. */ { int i; printf(" \""); for (i=0; s[i]; ++i) { /* Certain characters are quoted. */ if (s[i] == '\\') printf("\\\\"); else if (s[i] == '"') printf("\\\""); else if (s[i] == '\n') printf("\\n"); /* Others are just printed as such. */ else printf("%c", s[i]); /* Also insert occasional line breaks. */ if (i % 48 == 47) printf("\"\n \""); } printf("\""); } /* What follows is a string representation of the program code, * from beginning to end (formatted as per the quote() function * above), except that the string _itself_ is coded as two * consecutive '@' characters. */ const char progdata[] = "/* A simple quine (self-printing program), in st" "andard C. */\n\n/* Note: in designing this quine, " "we have tried to make the code clear\n * and read" "able, not concise and obscure as many quines are" ", so that\n * the general principle can be made c" "lear at the expense of length.\n * In a nutshell:" " use the same data structure (called \"progdata\"\n" " * below) to output the program code (which it r" "epresents) and its own\n * textual representation" ". */\n\n#include <stdio.h>\n\nvoid quote(const char " "*s)\n /* This function takes a character stri" "ng s and prints the\n * textual representati" "on of s as it might appear formatted\n * in " "C code. */\n{\n int i;\n\n printf(\" \\\"\");\n " " for (i=0; s[i]; ++i) {\n /* Certain cha" "racters are quoted. */\n if (s[i] == '\\\\')" "\n printf(\"\\\\\\\\\");\n else if (s[" "i] == '\"')\n printf(\"\\\\\\\"\");\n e" "lse if (s[i] == '\\n')\n printf(\"\\\\n\");" "\n /* Others are just printed as such. */\n" " else\n printf(\"%c\", s[i]);\n " " /* Also insert occasional line breaks. */\n " " if (i % 48 == 47)\n printf(\"\\\"\\" "n \\\"\");\n }\n printf(\"\\\"\");\n}\n\n/* What fo" "llows is a string representation of the program " "code,\n * from beginning to end (formatted as per" " the quote() function\n * above), except that the" " string _itself_ is coded as two\n * consecutive " "'@' characters. */\nconst char progdata[] =\n@@;\n\n" "int main(void)\n /* The program itself... */\n" "{\n int i;\n\n /* Print the program code, cha" "racter by character. */\n for (i=0; progdata[i" "]; ++i) {\n if (progdata[i] == '@' && prog" "data[i+1] == '@')\n /* We encounter tw" "o '@' signs, so we must print the quoted\n " " * form of the program code. */\n {\n " " quote(progdata); /* Quote all. */\n" " i++; /* Skip second '" "@'. */\n } else\n printf(\"%c\", p" "rogdata[i]); /* Print character. */\n }\n r" "eturn 0;\n}\n"; int main(void) /* The program itself... */ { int i; /* Print the program code, character by character. */ for (i=0; progdata[i]; ++i) { if (progdata[i] == '@' && progdata[i+1] == '@') /* We encounter two '@' signs, so we must print the quoted * form of the program code. */ { quote(progdata); /* Quote all. */ i++; /* Skip second '@'. */ } else printf("%c", progdata[i]); /* Print character. */ } return 0; }

Nitrux OS
I feel that this piece of wonder isn't getting the recognition it deserves.
One of the most beautiful UIs out there, revolutionary tech like znx(booting from the main iso ALWAYS and keeping user data across reboots, in a nutshell) and it has weird ass virtualization stuff that allowed them to run windows with very little virtualization overhead(tech details yet to announce).

Imma stop here before getting labelled another fanboy, just check it out and see for yourself
Thanks for reading, i use arch btw

Least successful...

In a nutshell, an multi version http client for a elasticsearch.

It supported ES 1.7 up to v7.

With an reduced future set, but all in all it allowed doing everything ES offered - just not for one version, rather the whole monty.

For various reasons I wasn't allowed to opensource that...

Which brings me to the least successful part. The client is a beast and would be a blessing for a lot of people I'd guess, but it's sadly covered by more legalese than one could imagine.

Think of legalese as in "Angel - Wolfram and Heart" legalese. I wouldn't be surprised if some part of the contract was written in blood.

... And least successful as in: Nope. Never gonna do that again.

Abstractions necessary for supporting multiple versions are are really painful.

Having an E2E test suite consuming > 64 Gigabyte of RAM for testing against several ES docker instances in parallel isn't fun.

Nothing of that project was fun.

Still gives me nightmares.

(NDA expired short time ago)

2017 in a nutshell for me:

New year new me! This year I'm going to use a version control system!

Uses git for 3 hours and feels proud. Later forgets about it and never uses it again

Programming in a nutshell:

"I changed nothing and it now doesn't work. Why?"
"I changed nothing and it now works. Why?"

I work on a small team, and we recently got an artist on it.

The artist has lights on, but nobody is home syndrome and it is driving me nuts.

This guy took 10 iterations on a model where the main request was to fucking change the fucking UV mapping. Here is how that went in a nutshell:

1. Hey, the model is ok, the guy needs a cape with some bones in it. The cape needs to share the material, here is the material, cape already on it. We also need like 8 animations.
1a. No cape visible, animations half done, and done shitty.
2. Correct the animations and all the above points asap. Ok?
2a. Few more animations 1 half corrected wrong, wonky exports. Has cape
3. Again, same.
3a. I got the wrong corrections, cape doesn,t move. Uv wrong and seperate material. Aaaarrrggg

It litterally took 7 more of those loops and now we have it going in 1 material and 5 wonky but workable animations. And the next character half of the same shit happens all over again. Fuck me, fuck him. Fuck this, i hate artists. I made a fucking list what is so hard?!

Alright, let's talk about Scrum Masters. Honestly, I just can't wrap my head around why they're even a thing. It's like someone decided to invent a job title for a role that's already covered by other folks on the team.

I mean, think about it. Who's usually sorting out the team's issues, making sure everyone's on the same page, and keeping the project on track? That's right, it's the project manager or the lead dev. They're already in the trenches, dealing with the nitty-gritty, so why do we need this extra layer?

And don't even get me started on this "servant-leader" nonsense. It's like they're trying to be the team's buddy, but they've got no real power to make things happen. It's like being a king without a crown. Who's going to respect that?

Plus, having a Scrum Master often just leads to more red tape. Instead of getting stuff done, we're stuck in endless meetings, talking about process this and methodology that. It's like we're more focused on how we work instead of actually working.

The best teams I've seen don't need a Scrum Master to babysit them. They need a real leader, someone who's not afraid to make the tough calls and who can give them the tools they need to kick ass and take names.

So, in a nutshell, I think Scrum Masters are about as useful as a chocolate teapot. It's high time we ditched this outdated role and got back to doing what we do best: building awesome stuff.

1/2 dev and a fair warning: do not go into the comments.
You're going anyway? Good.

I began trying to figure out how to use stable diffusion out of boredom. Couldn't do shit at first, but after messing around for a few days I'm starting to get the hang of it.

Writing long prompts gets tiresome, though. Think I can build myself a tool to help with this. Nothing fancy. A local database to hold trees of tokens, associate each tree to an ID, like say <class 'path'> or some such. Essentially, you use this to save a description of any size.

The rest is textual substitution, which is trivial in devil-speak. Off the top of my head:
my $RE=qr{\< (?<class> [^\s]+) \s+ ' (?<path>) [^'] '\>}x;

And then? match |> fetch(validate) |> replace, recurse. Say:
while ($in =~ $RE) {
my $tree=db->fetch $+{class},$+{path};
$in=~ s[$RE][$tree];
};

Is that it? As far the substitution goes, then yeah, more or less. We have to check that a tree's definition does not recurse for this to work though, but I would do that __before__ dumping the tree to disk, not after.

There is most likely an upper limit to how much abstraction can be achieved this way, one can only get so specific before the algorithm starts tripping balls I reckon, the point here is just reaching that limit sooner.

So pasting lists of tokens, in a nutshell. Not a novel idea. I'd just be making it easier for myself. I'd rather reference things by name, and I'd rather not define what a name means more than once. So if I've already detailed what a Nazgul is, for instance, then I'd like to reuse it. Copy, paste, good times.

Do promise to slay me in combat should you ever catch me using the term "prompt engineering" unironically, what a stupid fucking joke.

Anyway, the other half, so !dev and I repeat the warning, just out of courtesy. I don't think it needs to be here, as this is all fairly mild imagery, but just in case.

I felt disappointed that a cursed image would scare me when I've seen far worse shit. So I began experimenting, seeing if I could replicate the result. No luck yet, but I think we're getting somewhere.

Our mission is clearly the bronwning of pants, that much is clear. But how do we come to understand fear? I don't know. "Scaring" seems fairly subjective.

But I fear what I know to be real,
And I believe my own two eyes.

Smartphone users in 2012: "Non-replaceable batteries need to be outlawed."

Politicians in 2027: "Were… were starting to think about it. Have some patience."

Politics in a nutshell.

When I was 12 i had a Friday afternoon course, as they called it, in QBasic. Nothing fancy but I learned that 'I wanted to work with computers'.
10 years later I got my first programming job. It was with the old Cognos Powerhouse language on OpenVMS. Does anyone remember that?
I had that job for 4 years and it took me another 10 (and several other IT jobs) before I started to learn Java, which I do now for 2 years.

That's my career story in a tiny nutshell 😎

Hmm, this front-end framework looks great, it would be a shame if... "the latest version of jQuery is required"... Well, fuck you then, let's see the next one.

My day in a nutshell.

I think I had another insight.

Long story short, you're not the main character. You're not an NPC either. You're a spotlight!

Looking at yourself in the present doesn't make sense. You're not gonna understand yourself this way. In general, you're nothing but a history. In the present, you're an unbiased observer reading a history book.

This way of thinking is hard to pick up, but in a nutshell, for every emotion you feel, ask yourself: "Where did this feeling come from?"

This framework immediately takes the guilt away. It is what it is, the history doesn't entertain what-ifs. Once you memorize your own history word by word, only then you can really understand yourself and be free of trauma.

School software development project in a nutshell:

You will need to gather the requirements from us by ways of an interview, built the documentation for it, we'll sign it and that's what you have to build.
...
We were supposed to get that signature 3 weeks ago, but they decided to not sign yet because they want to make late changes to the project whenever they want, yet we have to finish the build of this in 7 weeks... Seriously? That's what we have to work with.

Any working devs that recognize this situation at work and not at school?

A bit long, sorry.

I "inherited" an A+ certification book from my older brother over 10 years ago after he saw me meddling with some old computers that still used SIMM's. I still lived in my native country at the time and got my A+ certification through my high school when I moved to the US. I knew before I got the book that my career would revolve around IT.

I learned HTML and CSS right after I finished high school and started working with JS and PHP because of WordPress a year later. To this day I still help family and friends with IT related stuff, but after digging into web development I made it my main focus. I am now working on my CS degree after failing at college years ago because of laziness and procrastination. I also work at an amazing startup as a software engineer for the web. That's it in a nutshell, questions are welcome.

Can I get a stress ball? 😅

Everything we have in life is a set of illusions, one seemingly more real than the other. When a child pees themselves in their sleep, they pee in a perfectly real bucket. They hear a steady, real sound of urine hitting the wall, confirming they didn’t miss, but somehow, it doesn’t sit well with them, and they doubt. A serious, full-grown adult is different in just one thing — they also shit themselves.

They lack that doubt that brings the child closer to the truth. Instead, adults have a so-called “scientific worldview”, that, in a nutshell, is about how the bucket is real because of the sound, and the sound is real because of the bucket, and thus, we all should be working 24/7.

To help a serious, full-grown adult wake up from this reality, death exists.

Which skills and platform do I need to focus as a ASP.NET back end developer? The .NET development environment is so massive, I really don't know from where do I need to start. I do know basic C# syntax and was studying C# 7.0 in a Nutshell and stopped temporarily because it introduced too much concept that I don't need for now. Any advice will be appreciated. Thank you!

There are two kinds of art and leisure: Apollonian and Dionysian. Apollo was the god of light, knowledge and other such things. Dionysus was the god of wine and ritual madness. In a nutshell, the beauty of the stars in the sky is Apollonian, and the beauty of nice juicy ass is Dionysian.

My info landscape was too damn Dionysian lately. I don’t even use TikTok or Instagram. I mean music I listened to, like aggressive dumb rap, bad slang, swearing… Wherever you look, there are Cardi B’s and Kim K’s, with their ugly eyelashes, ugly makeup, ugly inflated lips, ugly voice, ugly things they say. Watching the dumbest shit ever on YouTube. The louder you scream, the funnier the joke. Also, the number one content is some people tearing down some other people: penguinz0 destroying someone again, debunk channels, drama…

Dionysian things can be attractive and comfortable, because they speak to our animal part. In a way, Dionysian is natural. But not everything that is natural is good.

I gave my info landscape an Apollonian cleansing. Unsubscribed from a lot of debunking channels. Changed the way I speak, adjusted my vocabulary. Deleted a lot of music from my library. Went from 6ix9ine to Pink Floyd, Sting and Dire Straits.

It all started two weeks ago. I feel… different, but not necessarily better. Time will tell.

Want to send an email? Sure thing, how about you configure first a DKIM, DMARC, SPF and some reverse DNS. Otherwise your mail can go fuck itself, because it won't even make it to the spam folder. Even if you do all these time consuming fuckwit tasks I might just mark your mail as spam. Because fuck you, that's why.

Sending mail to Gmail in a nutshell.