Worst experience with higher ups:

The Office team at Microsoft suddenly woke up to the possibility of innovation from the grounds up. We were asked to come up with ideas. The best ideas were to be shortlisted by management.

That's what i had a problem with. People are generally bad at dertermining what will work. So instead of managenst shortlisting, everyone should have run cheap experiments with their ideas and we could then double down on the ones that showed promise. That's what is done at all internet companies. But the Office team's culture hadn't changed from the boxed software days.

I was asked to have faith in the judgement of management.

Well, Ballamer didn't let Office develop mobile apps for Android and Apple. When Nadella took over, he fixed that mistake. But because competitors had already gotten ahead, the Office team had to work on Saturdays for almost a year to ship it quickly. Meaning employees having to unnecessarily sacrifice their family time because of a strategic blunder by the highest management.

So excuse me if I don't have faith in the judgement of management.

1. If your contract allows it (and it should), get more involved in public dev community. Your employer benefits greatly from making a small closed source core product, with a giant open source ecosystem around it. Write public articles. Working in a community larger than one single business is fun.

2. Start a company coding club, a "labs" division, work in a slightly more exotic language. Great if your employer gives you time, but using some of your own is worth it too. Work on non critical tools, creative experiments. Sometimes you stumble onto incredibly valuable ideas which would never have popped up if you had strictly followed stakeholder requirements.

3. Listen to your body. If you feel restless, go for a run. If you feel tired, take a nap. If you're stuck, wander around the company. If you feel down, go find a place with more than a dozen trees. And always have a notepad nearby for doodling!

Fuck China.

Fuck the U.S. government.

Fuck the UK and Australia and all the other governments for taking advantage of the crisis of the last two years to get more power and money for their elites.

Fuck them all for starting COVID with their unsanctioned and unethical “gain of function” lab experiments and creating so much chaos that nobody really has a chance anymore at living the life they had dreamed of or so carefully planned for.

Fuck them for the out of control spending and money printing and inflation and even messing around with trying to regulate and tax crypto so we don’t have any kind of escape valve to live a normal, happy life.

Because of them, I can’t even enjoy my time off work. Even if I could plan a vacation that wouldn’t have to be canceled due to an outbreak or resultant supply chain issues, I can’t travel without severe restrictions that make it miserable and not worth the trouble.

Fuck them for making everyone into stupid monkeys fighting over opinions about data that is incomplete, misunderstood, misrepresented, or downright fixed toward a specific pharma-fascist authoritarian outcome.

And fuck them especially for being hypocrites and going to parties and generally not following their own rules they made for us when they think we’re not watching, and then persecuting and prosecuting us when we dare do the same.

Fuck ‘em all. I’m so done.

My first dev job was a paid internship at Oak Ridge National Laboratory. But I wasn't in the computing division with the supercomputer and the 30-foot 18-screen wall display. In a way, I was doing something more exciting. I was in the Hollifield Radioactive Ion Beam Facility.

That meant that I was working next to a radioactive ray gun that they fired at different targets to try and make new kinds of particles. To refine the beam components, there was a tower with the world's highest voltage Van de Graf generator at 25,000 kilovolts. I got training on how to put on a radiation suit, and was told that if I got locked in the wrong room and red lights began to flash, I had about five seconds to run to the far wall and push the E-stop, before I got irradiated and died slowly over the next five weeks.

But, I was reassured, that never happened. Radiation leaks are rare too (that's why we wore dosimeters). More likely, there would be a leak in the generator tower. To explain why that's bad, that tower wasn't filled with normal air. 25,000 kilovolts would punch through that like nothing, arc against the walls, and we'd lose the electric charge. No, instead, the tower was filled to a few atmospheres of pressure with sulfur hexafluoride gas. You know how helium makes your voice go up? This stuff makes your voice go down. It's heavier than air, and it kills you by displacing and starving your lungs of oxygen.

So, while I was happily coding away on PHP, CSS and the Bash shell, making a log book for all the ion gun settings and targets the scientists used in their experiments, I was keeping an ear out for the oxygen alarm. I had a blast!

This was typical for me:

Yesterday evening I was installing a webserver on my Raspberry Pi for experiments with WordPress. I began some days ago, but I had to stop because the downloads took at least to long.

So I started to logi in:

Username: Raspberry
Password: Pi
-> False Password

Wondering why it is not working a tried again. Same result. After some time I remembered that I changed my password.

Username: Raspberry
Password: Ih4G2tgY*
-> false password

*example
Tried again. Still false password. Then I remembered, that I used my another standard password.

Username: Raspberry
Password: U2gra94hY*
-> false password

After that I felt a mix of angry and helplessness. After some other failed attempts I gave up.

I formatted the SD-Card and installed Raspian again.I started my Pi

Username: Raspberry
Password: Pi
-> false password

My thought: WTF, why does this not work!!

This was the moment when I got the brainwave that the Username wasn't Raspberry, it's Pi.

Username: Pi
Password: Raspberry
-> access

Then I hated myself.

"Kiki, I want you to, for the first time of your career at %company%, quit worrying about deadlines and just wander free. Forget about due projects, forget about everything, and just do your crazy experiments till the end of this month."

This was the one-to-one with our CEO today. Yes, I'm being paid to do whatever I want without time restrictions, as long as it is related to my field.

And you know what? At this stage of my life, I don't even want to exploit that, to weasel my way around definitions and justify doing nothing. I legit have three AI experiments to run, I have money to run them, I have time, and I for sure have motivation.

Good workplace is when doing nothing isn't the most desirable thing to do.

!rant & story_time
This happend to the startup I was working for at ~2011. I was a junior Android dev, working on a very popular app.
During experiments for a new feature, I discovered that the system AlarmManager has a serious bug - you can set a repeating alarm with interval=0ms. If your app takes more then 1 ms to handle the Intent, then the AlarmManager will start to fill up the intent Queue, with unexpected results to the OS. causing it to slow down, and reboot when it ran out of Ram. Why? my guess was that because the AlarmManager was part of the OS, then any issues caused by it caused the system process to ran out of ram, crashing it, and the whole system with it. the real kicker was that even after a reboot, the AlarmManager still had Intents queued, causing the device to bootloop for a while, untill the queue was cleared. My boss decided to report the problem to google, as this was an issue in the OS. I built an example app, that caused the crash 10-30 seconds after starting, and submitted to Google. Google responded later that day with "not an issue, no one will ever do this".
Well... At this point I decided to review the autoupdate feature in our app, to make sure this will not happen to us. We just released a new feature where a user can set an update schedule option in the app settings - where you could setup a daily, weekly, or hourly update for the app. after reviewing it, It looked good, and the issue was not triggered in the manual QA I did. So, it was all good. And we released an updated version to the store.
After we did an update-install, we discoverd that, there was a provlem reading the previous version SharedPrefs value for the update schdule settings, and the value defaulted to 0...
the result was, our app caused all our users to go into a bootloop, and because the alarm was reset when the devices booted up, the bootloop could only be solved in a factory reset, or removing our app, before the device rebooted, and then waiting a few reboot cycles.
We lost 50 places in the market, and it took us 6 months to get back to where we were.

It was not my fault, but it sucked big time!

Believe me I didn't code today... full day with my daughter... video recording for her youtube channel... science experiments... castle... and .. and ...

Today our manager agreed on buying a second hand server for the development team to play around with and run personal experiments.

We found a dual cpu (6 core 2.8 GHz) system with 24 gigs of ram.

Let the fun begin!

Staring at cursed blinking cursors.
Repairing work of worst thinking workers
Reverse merges or it'll murder the servers, it nurtures despair
Amateur managers, dimwitted savages interrupt all of us janitors
Cleaning up damages, spills and experiments using skills in embarrassment
Explicit foulness, in a minute it's straight to the bowels with weapons of limitless vowels
A bittersweet hateful machete, eviscerates stateful spaghetti
The slow disease flowing from keys knowing it's going to please
The growing unease, no one agrees, there's no guarantees with your useless degrees
Need more drugs, keyboard's crawling with bugs, falling as I chug
A bottle of cognac gotta love all the hacks, no poise for code that lacks
All the noise, gotta relax, before I destroy the syntax.

Excuse me for not making sense.
Too gloomy, aching and tense.

Using 10% React with the rest in Jquery. Importing a giant legacy CSS blob in a newly made SCSS file. Two thirds of the API documentation in docblocks, the rest in Markdown files. Half of the repositories in Github, the other half in Bitbucket. The root of every project littered with ymls and jsons and readmes of stupidly named tools no one has ever heard of.

Fuck your partial refactoring, fuck your little experiments, fuck all this half work. I'm so done with this shit. 😡

Started showing my brother some deep learning tutorials and I have him reading a book.

I really need for him to realize how smart he is. He was never academically inclined. I always told my mother that it had to do with the same dislike of school that I always had and how a couple of really shitty teachers could run one's motivation to the ground.

I always found him brilliant. Had a good standing with common sense amd logical thinking. He was interested in math for a while(same as me) but school made him hate it. He managed to pass all the state exams needed to graduate from H.S and was able to succesfully pass the military ASVAB with a very good grade.

But after H.S he went down the drain with what he wanted to do.

I love my brother and really want him to find out just how smart I think he is and this would probably be one of my biggest experiments with him. Maybe, just maybe if I get him to realize that he can understand these advanced concepts without a teacher his(fear?) Of school might go away enough for him to give it a second go. Fuck man I don't even need for him to go and get a B.S in comp sci, an associate degree would be just fine. It can be on anything, I just want him to do something.

Sometimes I feel as if this was my fault. At one point he told me that he feels shadowed by my grades. And my family was always proud of what I did in H.S and at uni. I feel(sometimes) that I should have paid more attention to him as he was going to school, help out a little more and encourage him more.

He feels as if he is meant for a dead end miserable working life, and I really can't bear the idea of him wasting himself away to something like that.

I really hope this shit works man...i really need for this to work, he doesn't even need to like it, just realize that it is possible.

Root experiments.

Spiced rum, kahlua, grand mariner, chocolate liquor, milk, ice. Tastes like house paint, and not in the good way like protein bars. Do not recommend. Better with more milk, but still meh.

Spiced rum, kahlua, triple sec, milk, ice. Tastes like orange milk with coffee. Pretty nice.

Spiced rum, ice. Tastes like a faint memory of heaven. Amazing grace, hallelujah.

"So Alecx, how did you solve the issues with the data provided to you by hr for <X> application?"

Said the VP of my institution in charge of my department.

"It was complex sir, I could not figure out much of the general ideas of the data schema since it came from a bunch of people not trained in I.T (HR) and as such I had to do some experiments in the data to find the relationships with the data, this brought about 4 different relations in the data, the program determined them for me based on the most common type of data, the model deemed it a "user", from that I just extracted the information that I needed, and generated the tables through Golang's gorm"

VP nodding and listening intently...."how did you make those relationships?" me "I started a simple pattern recognition module through supervised mach..." VP: Machine learning, that sounds like A.I

Me: "Yes sir, it was, but the problem was fairly easy for the schema to determ.." VP: A.I, at our institution, back in my day it was a dream to have such technology, you are the director of web tech, what is it to you to know of this?"

Me: "I just like to experiment with new stuff, it was the easiest rout to determine these things, I just felt that i should use it if I can"

VP: "This is amazing, I'll go by your office later"

Dude speaks wonders of me. The idea was simple, read through the CSV that was provided to me, have the parsing done in a notebook, make it determine the relationships in the data and spout out a bunch of JSON that I could use. Hook it up to a simple gorm golang script and generate the tables for that. Much simpler than the bullshit that we have in php. I used this to create a new database since the previous application had issues. The app will still have a php frontend and backend, but now I don't leave the parsing of the data to php, which quite frankly, php sucks for imho. The Python codebase will then create the json files through the predictive modeling (98% accuaracy) and then the go program will populate the db for me.

There are also some node scripts that help test the data since the data is json.

All in all a good day of work. The VP seems scared since he knows no one on this side of town knows about this kind of tech. Me? I am just happy I get to experiment. Y'all should have seen his face when I showed him a rather large app written in Clojure, the man just went 0.0 when he saw Lisp code.

I think I scare him.

I need a folder for unsorted unfinished programs to sort them out of sorted unfinished programs. Also, I have an "old" folder inside of "old" folder. On both computers.

Yesterday I did some experiments with my lab bench power supply to see if everything was working as it should, and whether my newly acquired laptop (old business laptop from 2004) would still power up. Noticed that it did, and left the thing charging for a while - its battery was completely drained. But after letting it sit for a few hours, one of my switches wouldn't turn off anymore.

The lab bench power supply has a 250V 2.5A (625W) rated switch on the AC side, connected to a 50V 10A (500W) AC-DC power supply. The DC side of that is then connected to 2 DPS5005 units, of which one was driving 50W of power into the laptop.

The experiment went reasonably well, the AC-DC power supply was loud but stayed cool like a cucumber. The switch however wouldn't turn off anymore after a few hours. Today I've desoldered that and put on a new one, and did a failure analysis. Turns out that it was a rocker switch (so there's a little nub in there that moves a piece of metal back and forth) and that the contacts of the switch (the piece of metal and the inside of the connector piece) were welded together.

However, the only thing that I know of that causes this welding is when loads are switched off, and an arc is generated. This wasn't the case here - it was just kept on for a couple of hours, with (accounting for power losses across the circuits) 80W going through it at most. I never expected that to cause a weld. Any clue as to why this happened? It really boggles my mind, and I don't want the switch that's currently in there to face the same fate.

We developed an application and deployed on production (but not launched)
And business team already created lot of garbage or dummy data. Reporting systems are huge pile of bars, stats and shit.

Now, has to destroy and clean production.

Already advise them to do experiments or testing dev or staging.

Damn. First time in my career experienced this. Has to delete production.

FUCK YOU MAGNETO!!!!!

what a backstabing cunt

imagine you're trying to prevent world war 3 from happening with someone you've been training for months.

out of nowhere, this FUCKING PICE OF SHIT decides to become a vilain.

in the midst of the event he tries to deflect a bullet that ricochets into my spine.
thanks asshole, now I can't walk

i thought we were friends man, we bonded over painful shit

like ok, they killed your mom and made experiments with you,

but it was just the NAZIS, LITERALLY EVERYBODY HATES THEM.
take it out on them, not the entire humanity bro

you unlocked your powers thanks to me, you couldn't even lift the toilet seat.

and you don't even give a fuck about mutants, you power hungry bitch

you only care about total domination

"oh no, someone save us from this mutant whose real name is eric"
im so scared right now

I think that two criterias are important:

- don't block my productivity
- author should have his userbase in mind

1) Some simple anti examples:

- Windows popping up a big fat blue screen screaming for updates. Like... Go suck some donkey balls you stupid shit that's totally irritating you arsehole.
- Graphical tools having no UI concept. E.g. Adobes PDF reader - which was minimalized in it's UI and it became just unbearable pain. When the concept is to castrate the user in it's abilities and call the concept intuitive, it's not a concept it's shit. Other examples are e.g. GEdit - which was severely massacred in Gnome 3 if I remember correctly (never touched Gnome ever again. I was really put off because their concept just alienated me)
- Having an UI concept but no consistency. Eg. looking at a lot of large web apps, especially Atlassian software.
Too many times I had e.g. a simple HTML form. In menu 1 you could use enter. In menu 2 Enter does not work. in another menu Enter works, but it doesn't submit the form it instead submits the whole page... Which can end in clusterfuck.
Yaaayyyy.
- Keyboard usage not possible at all.
It becomes a sad majority.... Pressing tab, not switching between form fields. Looking for keyboard shortcuts, not finding any. Yes, it's a graphical interface. But the charm of 16 bit interfaces (YES. I'm praising DOS interfaces) was that once you memorized the necessary keyboard strokes... You were faster than lightning. Ever seen e.g. a good pharmacist, receptionist or warehouse clerk... most of the software is completely based on short keyboard strokes, eg. for a receptionist at a doctor for the ICD code / pharmaceutical search et cetera.
- don't poop rainbows. I mean it.
I love colors. When they make sense. but when I use some software, e.g. netdata, I think an epilepsy warning would be fair. Too. Many. Neon. Colors. -.-

2) It should be obvious... But it's become a burden.

E.g. when asked for a release as there were some fixes... Don't point to the install from master script. Maybe you like it rolling release style - but don't enforce it please. It's hard to use SHA256 hash as a version number and shortening the hash might be a bad idea.

Don't start experiments. If it works - don't throw everything over board without good reasons. E.g. my previous example of GEdit: Turning a valuable text editor into a minimalistic unusable piece of crap and calling it a genius idea for the sake of simplicity... Nope. You murdered a successful product.
Gnome 3 felt like a complete experiment and judging from the last years of changes in the news it was an rather unsuccessful one... As they gave up quite a few of their ideas.

When doing design stuff or other big changes make it a community event or at least put a poll up on the github page. Even If it's an small user base, listen to them instead of just randomly fucking them over.
--
One of my favorite projects is a texteditor called Kate from KDE.

It has a ton of features, could even be seen as a small IDE. The reason I love it because one of the original authors still cares for his creation and ... It never failed me. I use Kate since over 20 years now I think... Oo

Another example is the git cli. It's simple and yet powerful. git add -i is e.g. a thing I really really really love. (memorize the keyboard shortcuts and you'll chunk up large commits faster than flash.

Curl. Yes. The (http) download tool. It's author still cares. It's another tool I use since 20 years. And it has given me a deep insight of how HTTP worked, new protocols and again. It never failed me. It is such a fucking versatile thing. TLS debugging / performance measurements / what the frigging fuck is going on here. Take curl. Find it out.

My worst enemies....

Git based clients. I just hate them. Mostly because they fill the niche of explaining things (good) but completely nuke the learning of git (very bad). You can do any git action without understanding what you do and even worse... They encourage bad workflows.
I've seen great devs completely fucking up git and crying because they had really no fucking clue what git actually does. The UI lead them on the worst and darkest path imaginable. :(

Atlassian products. On the one hand... They're not total shit. But the mass of bugs and the complete lack of interest of Atlassian towards their customers and the cloud movement.... Ouch. Just ouch.

I had to deal with a lot of completely borked up instances and could trace it back to a bug tracking entry / atlassian, 2 - 3 years old with the comment: vote for this, we'll work on a Bugfix. Go fuck yourself you pisswads.

Microsoft Office / Windows. Oh boy.
I could fill entire days of monologues.
It's bad, hmkay?

XEN.
This is not bad.
This is more like kill it before it lays eggs.
The deeper I got into XEN, the more I wanted to lay in a bathtub full of acid to scrub of the feelings of shame... How could anyone call this good?!?????

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

Most successful? Well, this one kinda is...

So I just started working at the company and my manager has a project for me. There are almost no requirements except:
- I want a wireless device that I can put in a box
- I want to be able to know where that device is with enough accuracy to be able to determine in which box the device was put in if multiple boxes were standing together

So, I had to make a real time localization system. RTLS.
A solo project.

Ok, first a lot of experiments. What will the localization technique be? Which radio are we going to use?
How will the communication be structured?

After about two months I had tested a lot, but hadn't found THE solution. So I convinced my manager to try out UWB radio with Time Difference Of Arrival as localization technique. This couldn't be thrown together quickly because it needed more setup.

Two months later I had a working proof of concept. It had a lot of problems because we needed to distribute a clock signal because the radio listeners needed to be sub-nanosecond synchronous to achieve the accuracy my manager wanted. That clock signal wasn't great we later found out.

The results were good enough to continue to work on a prototype.
This time all wired communication would be over ethernet and we'd use PTP to synchronize the time.

Lockdown started.

There was a lot of trouble with getting the radio chip to work on the prototype, ethernet was tricky and the PTP turned out to be not accurate enough. A lot of dev work went into getting everything right.

A year and 5 hardware revisions later I had something that worked pretty well!
All time synchronization was done hybridly on the anchors and server where the best path to the time master was dynamically found.

Everything was synchronized to the subnanosecond. In my bedroom where I had my test setup I achieved an accuracy of about 30cm in 3d. This was awesome!

It was time to order the actual prototype and start testing it for real in one of the factory halls.

The order was made for 40 anchors and an appointment was made for the installation in the hall.

Suddenly my manager is fired.

Oh...
Ehh... That sucks. Well, let's just continue.

The hardware arrives and I prepare everything. Everything is ready and I'm pretty nervous. I've put all my expertise in this project. This is gonna make my career at this company.

Two weeks before the installation was to take place, not even a month after my manager was fired, I hear that my project was shelved.

...
...

Fuck

"We're not prioritizing this project right now" they said.

...

It would've been so great! And they took it away.
Including my salary and hardware dev cost, this project so far has cost them over €120k and they just shelved it.

I was put on other projects and they did try to find me something that suited me.

But I felt so betrayed and the projects we're not to my liking, so after another 2-3 months I quit and went to my current job.

It would've so nice and they ruined it.
Everything was made with Rust. Tags, anchors, RTLS server, web server & web frontend.

So yeah, sorry for the rambling.

"Eh why my experiment won't stop?" Oh right I didn't write code that will stop it
*facepalm*

So for a while I have wanted to build a raspberry pi cluster. In the spirit of shia labeouf I got started last saturday.

I had two pies lying around so I figured I'd run some experiments before I invested in a lot of hardware. After about a day I had turned the two pies into a shared cluster when disaster struck....

I had completely ignored the fact that you cannot run 32 or 64bit software on an arm processor (I know... I'm a java developer). So when I booted my service and the load balancer, I found that nothing worked. So pretty bumbed out, I quit the project.

Later that day I found a crazy guy who had bought a batch of 400 small form factor PSUs (300W) and internally I laughed at him a little. I mean, who's gonna sell 300W irregular power supplies. Then, just as I was about to go to bed I found this guy, he was selling from a batch of CPU-onboard motherboard for 10 bucks each and everything clicked!

I did some quick calculations and decided I could probably gather enough cash to get: 10 motherboards, 10 2GB ram dimms, 10 Sata disks and 14 PSU (in case some fail) and some misc hardware for networking and such.

So... Long story short, I am going to build a cluster computer, the first version is going to have 10 nodes and I am waiting for delivery right now!

when you have to use one language inside of another, and you basically have to call functions allowing you to call the other's language function within it, and you get the hell confused, since it gets harder and harder to see what is what and who can call who and how, and the compiler ofc. won't say anything about it since it only cares about the main language you are in and not the nesting of the other...
I just have no idea what I'm doing right now, or if my thought process and understanding of this is even close to where it is supposed to be.
D: I'm just confused and insecure about this right now....

time for experiments to figure this out, and get the hang of it

Like an idiot I decided to continue to grad school directly after finishing my undergrad (which I finished later than usual because I switched from a different major) only because my university has a pretty big deep learning lab with important professors.

After a year in, I realized that academia isn't that interesting to me and I'm nearing 30 with no real job experience so I'm hesitant to drop out for fear of not being able to find a job. Meanwhile, I'm dreading every morning when I have to go to the lab and do some BS experiments instead of being out there building stuff. I bought the hype and now I'm stuck.

1.
Accuracy 0.90 achieved so easily, makes me wonder if I've done something wrong. Lol.

2.
My neural net models are the only things in my life doing well. I think I chose the right career. Lol.

3.
Rerunning experiments is not fun. But getting better results is really... Ego stroking.

If you install your OS to one drive; can you remove the drive, then boot your OS in another computer off of that drive?

The year is 2025.

WSL2 still makes it a major, excruciating pain in the ass to expose a port over the network without having to look up the fucking command and think about the stupid cancerous networking model every time.

All I wanted to do was run some experiments with AI models on my gaming laptop using its GPU, and expose an API to my other laptop, having the latter as a client.

Guess I have to get fucking rid of Windows forever if I want a fucking usable computer.

The main reason I moved from Linux to macOS was that I grew up. If we count not just Linux experiments but prolonged usage, I was an avid Crunchbang fan. After it died, I moved to elementaryos.

What I want to say is, Linux can be very fun and educational when you're still in the uni. You have all the energy in the world, and you can afford to diverge from your daily routine for an hour to debug GPU drivers.
Now, the backbone of my life is keeping a very tight sleep schedule, taking meds on time, avoid infohazards, avoid scrolling on the web, all to remain in a very fragile state of balance that keeps the bipolar disorder away. I'm in the middle of all this, earning derealization (yes, I'm also autistic) every time I design a data model. All I want from my computer is to be treated like a careless, regular user, not like someone with a CS degree.

I use Sublime Merge instead of command line Git. I use Postico to explore PostgreSQL databases, not psql from my terminal. By the way, my terminal is not iTerm, Alacritty or some other such thing, my terminal is whatever came with my Mac, with whatever default settings.

Linux is crawling into a non-street-legal racecar's cockpit and strapping yourself in, ready to blast off. MacOS is your chauffeur, holding your old shaking hand as he helps you into your Maybach's backseat. They're different, and that's okay.
Can Maybach race? Well, it has a 621 HP V12, so if _you_ can race, it probably can too, but we all know it's not a racecar.

Windows? Windows is an SS officer, wearing the all too familiar Windows logo for swastika, throwing you into a gaswagen.

AI based epidemiologist with a simulator support to rerun it's experiment. It can identify trends in epidemic arrivals and provide solutions to stop it. Advantage will be faster and safer experiments, which is now done manually.

Installing Ubuntu on an old box of mine. May run well after all. Gonna make some experiments with Ruby and Python

Every time when I spend hours of thinking, investigations and experiments to find a solution to a problem...

And it ends up with a one line change in the git commit.

Always a strange feeling.

My most recent dream:

I come to the bookstore and see the 1000-something pages book called "We are not cucks". It's about how stoicism and how to defeat biases with thought experiments. The author is a German guy named ?.?.????rreize, I can't remember it precisely.

Everyone on the internet is discussing this book and why it is important. There are hashtags, influencers and virality.

Some time later the other book is released, 2500-something pages fundamental stuff called "We are cucks" with criticism of "We are not cucks" and whole new theory about why biases can't be defeated because of some "layers" IIRC.

I'm a practical learner. Usually i get myself a simple example from codeproject and play around with it.

I constantly switch between tutorials, documentation and doing it. Doing it makes me find questions and i can remember things better if i care about them, which happens if they are the answer to a question.

Within those experiments i build working example code and document it in a way that fits my needs. When i haven't done the stuff for some time, this self-made examples, help me continue where i was.

If you're coding, thinking and manually/auto debugging way too often several time a day, then you're likely to be suffering from "Geekonomous Schizophrenia", the Symptoms of that are:
.
1. You grow a habit to cut the B$ in real-life conversations.
.
2. You get instantaneously angry and disturbed when your mom/siblings/friends are interrupting you during your work.
.
3. Not to mention you cannot tolerate irrational words from Socially Accepted Normal Chaps (SANC)
.
4. You have nothing to speak unless a SANC starts the conversation themself.
.
5. You tend to correct these SANCs mid-semi-technical-talk whenever these do factual errors.
.
6. You get overwhelmingly excited and ecstatic to talk to someone of your expertise or at least a person who can intellectually handle your tech-blabbers and dev-rants!
.
7. You start doing minor-to-major experiments regarding different things in real life as you do virtually with your codes and try to predict the outcome the next time.
.
8. Best of all - whenever you are "loned-out" you don't feel lonely since you have many people and string of thoughts to talk to and inside your head there's a grand meeting going on.
.
Relatable? We're on same lines then! 😊

Well it's about my B.Tech project.
I had windows 7 and I had lots of imp data along with my project and I hadn't taken any backup of my project(not even report copy). So after successful completion of my project I thought let's play with OS and try other OS and that time I had rare awareness about data and OS too.

So I had copied my imp data(mainly friends party pics) into my friend's external HDD and I thought yeah I have clean chit now and literally I forgot about my project which was in C:/ drive.

So happily I had done experiments and enjoyed a lot and one day my my project partner asked about project copy and I had just given a smile.
RIP.
Happy Ending :D

Fuuuuuuuuucking hell. I have a program that parses and generates information from shit I have in a database into a csv file. Shit was simple enough to be done in Python.

Trying to present that shit into fucking pdf files? without drawing shit on x,y coordinates like a retard or without downloading a fucking obscure number of bs shit into the computer? on a fucking WINDOWS machine? fuuuuuuuuuuuuuuck.

Ok no problem. Do it in Node. WHAT IN THE HOLY FUCK more bullshit with drawing shit line by line. fuck this.

Lol not even going to touch java or c# for this, this is quick.

mmmh perl? nah, php? nah

Well shit I just need to generate data from a csv into a html template and send it away as a docume....go? ok lets....ah....done

Go wins again in my book ladies and gentlemen

It even has fewer lines of code than the php experiments

Google enslaved me to conduct their experiments on me, and now when I use a -webkit prefixed css property, I feel excruciating pain. They made me have intercourses with horses and bite my wife to death.

So far, I'm not a fan of Ubuntu touch on the pinephone. I think ill plan on switching to PostmarketOS this weekend. It looks more bare bones from what I've seen (admittedly not very much so far) but looks like it's for more features working. UBports has a ways to go yet.

Crystal ball!
A timeline until the first NBE-Citizen is elected president of the USA.

2031 - BlackRock launches their new large scale financial product, the "Robotic Business Development Company" (R-BDC), in which an AI is given billions of dollars to acquire, create and manage companies, replacing their C-suite executive bodies. The "Chief Executive Robot" (CER) is supervised by a board of human industry experts hired by BlackRock.
It is important to say that the employees, middle managers, accountants, lawyers, etc in an R-BDC are all human - it's only the CEO, CFO, COO and the rest of the gang that are overgrown chatbots.

2032 - R-BDCs are mostly focused on high-bureaucracy, non specialized but people-intensive legacy industries like steel mining, food services, urban transportation and government services like water and road management.

2033 - For the first time an R-BDC company is included in the S&P 500 index. If it's CER were human and paid the same as CEOs of equivalent companies, it would have become a billionaire.
Later in the year, two more R-BDC companies are included in the index. One of them was created by Apple and the other by JP Morgan.

2035 - An R-BDC company makes headlines for convincing BlackRock to dissolve it's review board. When finally given free reign, the CER immediately slices it's dividends and vastly increases low-level employee compensation. The company share prices crater, but BlackRock stands by its decision.
Later in the year, as a recession hits the entire market really hard, that company shows solid profits and fantastic sales. It becomes the first trillion-dolar R-BDC.

2037 - Most Americans' dream-job is in an R-BDC company, says ProPublica.

2038 - Congress passes the "Non-Biological Entities Liability" (NOBEL) Act, following a high profile case of employee harassment perpetrated by the CER of an R-BDC.
The act recognizes NBEs, for all legal liability purposes, as USA citizens.
This highly controversial legislation is upheld by the supreme court, and many believe it was first introduced by lobbyists as a way for large investors in R-BDCs to avoid legal responsibility.
Several class action lawsuits are filed against CERs that are now liable for insider trading. A few SCOTUS decisions set legal precedent that determinantes what exactly constitutes the parts of the same Non-Biological Entity.

2040 - As a decade ends and another begins, 35% of all companies in the US and 52% of the entire stock market are part of a R-BDC company or another. The McKinsey consulting group now offers "expert CER customization services".

2043 - Inspired by successful experiments in Canada, Australia and South Korea, the american state of Vermont is the first to amend it's constitution to allow municipalities to have Non-Biological Entities as city and government administrators. City councils are still humans-only.

2046 - The american state of Colorado becomes the first to allow unsupervised NBEs to assume state government executive positions. Several states follow soon after. Later in the year, the federal government replaces several administrative positions with NBEs.

2049 - The state of Texas passes legislation requiring the CERs of all companies with a presence in the state to be another entirely contained/processed within the state or to be supervised by a local human representative while acting within the state. Several states, including California, Florida and Washington, are discussing similar legislation.

2051 - Congress passes the SUNBELT Act (SUbmission [of] NBEs [to] Limits [and] Taxes) that vastly increases the liability of NBEs and taxes all manifestations of such entities. Most important, it requires
CERs of hundreds of companies manifest disagreeance, most warn that it might hurt employee satisfaction and company sales. Several companies disable their CERs entirely.

2053 - Public outrage after leaked interactions of human supervisors and company CERs show that the CERs tried to avoid the previous year's mass layoffs and pay cuts, but board members pressed on, disregarding concerns. Major investigations and boycotts further complicate matters, and many human workers go on strike until the company boards are dissolved and the CERs are reinstated.

2052 - Many local elections all over the country see different NBEs as contenders - and a NBE is expected to win in most races.

2054 - The SUNBELT Act is found unconstitutional by the supreme court, and most of its provisions are repealed.
This also legitimizes the elected NBE officials.

2058 - For the first time an NBE wins a seat in Congress, but is not allowed to keep it. Runoff elections are held.

2061 - Congress votes for allowing NBEs to hold federal legislative positions, as already allowed in the least populous states.

2062 - Several NBEs win Congress seats. In Europe, there are robot legislators since the 40's.

2064 - The first NBE presidential candidate loses the race.

2072 - The first NBE president is elected.

The life of a normal person is like waking up every day with a zero on the scale of suffering. You did something good — here are -20 points to that scale. Something bad happened — well, here are +10 points. Being a bipolar person, my life is like beginning every day with +500 suffer points. Every day is a devastating uphill battle to just break even.

Why live then?

You can't win. If you have a healthy sleep schedule, do sports and eat healthy, it's still +500 every day. One mistake like fucking up your sleep schedule — boom, you now start at +700.

In Japan, a new breakthrough in psychiatry is happening as they were able to tie bipolar disorder to a HHV6 herpesvirus messing up the operation of Parkinje cells in human brain, unreachable to the immune system because of blood-brain barrier. A nasal spray treatment is proposed. If successful, bipolar disorder could be cured forever.

Until an actual nasal spray is released, I decided to wait because it's a huge bummer killing myself only some three years before this breakthrough.

But if their experiments will never come to fruition and my conventional therapy will not be successful, I will kill myself.

I don't want to live like this.

I have this fried that gives me some advice on how to find work, he said i need to come up with a project idea as something to put on my CV and also as a way to learn front-end dev.

Easy enough if not for the fact that this project should be something that's actually useful and has some concept behind it (like, something that might seemingly work for a startup)

I've been raking my brain for a week now, and all i can come up with is small meme projects, neat but sort of inconsequential experiments, or things that might be useful to me but have no reason to be web-based.
I never realized how hard it is for me to come up with professional-sounding project ideas :D

I'm just not that kind of guy, i don't really have the drive or motivation to do anything professional: If people wanna use my rice or whatever spaghetti software i create they are welcome to, i'll even write them some documentation, but its just kinda out there on the internet because i like sharing. I don't really have any grand product ideas, nor do i really care about what other people think or need.

Assuming Mac: Alfred for OS such as searching and opening apps, using spaces to setup smart project areas, divvy app to quickly size and move around the windows, terminal shortcuts to open files in the OS or in an editor, transmit for hidden files and dragging between panes and server + occasional mounting for preprocessing, inbox-zero mentality, a properly setup google drive app so you don't email forked files back and fourth, beanstalk for deployment of larger stacks, surge.sh for targeted front-end sites, Ember CLI or brunch for build pipelines, CodePen for UI experiments outside of the project, slack instead of email, pick up the telephone and just call for clarification more often, stylus is easier to maintain then scss, hire designers that actually know what their job is if you can. For arduous WordPress administration, rightclick open in new tab for everything - or half your time will be pushing the back button, wp-migrate pro, and in general try to get out of WP when you can.

Some updates:

> Going to get another paper published (hopefully) once my exams end
> Got a intern, not a lot of money, ₹2L≈$2.6k per month for 2.5 months
> Will get a Mac from company for the intern(probably not new, and most likely will be taken back soon after the internship)
> Planning on entrepreneurship after getting a degree

Ohh and the rant:
1. Fucking sent me a 2 page list of links as "pre reads for internship" during my exams -- and intern will start soon after exams
2. Have missed 3 paper submission deadlines till now, hopefully will run more experiments on time this time and finally get that paper submitted (on 15th May)

tl;dr: why is it so hard to build a pc?😒

why is it so damn hard to find the right pc components for developing/image editing/gaming/...?😟
i've been googling around and watched many youtube videos on what components to buy/what to watch out for/tips/problems/etc...
i want to build a decent pc for web, mail, office, developing, running linux as VM (for experiments), edit images, doing most in multitasking (and maybe also play some games) ... basically everything, but i can't wrap my head around what to choose😟
every time when i think (for example) "ok, ryzen 5 2400G, that must be it!' there's always smth negative about it, come on!!🙄😤
i wanted to make an AMD setup for 1000€ max

i feel like as a developer/"kinda it guy" i know what i need, then again i feel dumb as fuck, not knowing what to choose and i'm almost certain i will pick smth wrong😪
do u guys have any suggestions for me/any help?

You people ever heard of the BeamNG game? The detailed vehicle physics simulation...

The question that has been bothering me lately is: why the hell are BeamNG videos so addictive 🤔 I get those videos sometimes in my YouTube feed; and once I start watching those, I usually cannot stop.

Like, the car with parts stripped from it over time. Or the truck carrying an ever-increasing number of rocks uphill. And the crashes, of course

But the question is: what do I find so fascinating about those videos? Why is it so hard to stop? On the surface, it is nothing special. Just some silly experiments involving vehicle physics

Weird; so weird... ☁️

I have done some experiments on my server in the past. It's a great way to learn new things. However, I am bound to make some mistakes and over time the sever becomes messier and messier.

A week ago I installed UNRAID on my machine and I love it! I can now have my critical infrastructure live and working in docker containers and vms.

Then if I want to do an experiment I spin up a VM in a couple of minutes to do my thing and remove it when I am done. No traces left!

I was trying to set up my own "cloud" for iot experiments. I planned to use Intel Edison with mqtt broker (using mosca) and a node js app for providing API for mobiles and browser. And also to do other book keeping.

I spent the half day trying figure how to expose these servers to internet.

I configured ddns in noip.com and ddns settings configured to it in my router.
Port forwarded to the local server services I needed.

And then tested. Worked perfectly on any device in my router connected network. Tested on mobile network. Bam! It fucking doesn't work.

Then connected another router.
Double port forwarded. Again worked perfectly on router network. And failed on mobile.
Tested if ddns is right. Did nslookup it was fine as fuck.
Then disabled port forwarding. Did dmz. Nope. Nadda. No luck.

Then scratched my head so hard that I lost more already losing hairs.

Then remembered about router hardware firewall. Disabled it.
Tested
And there it didn't work.
My dreams shattered like a fucking deer hit by car on highway.
Didn't work.
Then I see the IP pointing to my router in nslookup. Its 172.20.xx.xx. Its a fucking private IP.

My Asshole ISP is running another private network behind firewall. Which I fucking can't port forward
Now I think how much of a noob and idiot I am. Fuck this shit. Fuck all of these shit.
I am going for SaaS option for mqtt broker.
(Or help me?)
Once again.
Asshole ISP.
Fuck your firewall.
(PS: I had test the next day. FML)

Remember: all models are wrong, but some are useful. just because light is best approximated as a particle in one kind of experiments and as a wave in the other kind, doesn’t mean it _is_ a particle or a wave. try describing something — anything — in detail, then in greater detail still, again and again, and you’ll see how dull and inflexible is the language — the thing with which you interact with reality.

thus, once you go missing, no one will be looking for you — there is no one to look for. Nowhere, too. At least not in our cities and not on our maps.

commodore amiga 500, when I was 5 or 6.
what was the very first thing on it that i experienced, i don't know, but some things i remember:

Cannon Fodder 2
A-Train, a game that i played for months, it utterly fascinated me and i was utterly unable to keep my company afloat, because i was utterly unable to understand how the mechanics of the materials moving around worked (i still don't, actually, but in a different way)

some Apache simulator, which took us (me and father) literally a week to figure out how to get into the actual game from the main menu stylised as a military office. it took us several days to even realize it's the menu.

the Lotus Esprit 2 game, which we played regularly.

some Airbus simulator where i took two weeks of trial and error to figure out how to take off, without manual.

some experiments with midi sequencing and notation music programs.

how every two months, dad came with a 20page long list of programs and games from some pirate seller, which we would go through, mark stuff that sounded interesting (going by name only), then he would send it by post to him, and after a week, we would go take a package from post office full of floppies, literally like 200, and the next two or three weeks, we would be trying all of it out, seeing what the things we got were about, putting the good ones on one pile, the boring ones on another (cheap floppies for use)...

ah the magical times of wonder and exploration...

Every day is tempting to me..tempting to use some solutions i am not sure that i can handle it.

The Company i work for has an external IT Partner that does all the heavy lifting when it comes to our infrastructure, like installing servers, doing the installations and such. I mostly monitor it and do basic maintenance. Its all windows.

Recently i thought about adding a fifth Hyper V instance for an intranet webserver...based on some linux distro (probably ubuntu cause that is what i am familiar with). But i am not THAT familiar with ubuntu or any linux distro..buts its just the intranet and i already installed nginx and apache with success, what could go wrong?

today i sketched some intranet websoftware our production might find useful to collect data input from our workers (we are somewhat small so there is no big ERP software as of now). When thinking how to realize the data input i thought that maybe a basic raspberry and some cheap 1280x800 10.1 inch touch panels would be best..its very tempting, but on the other hand i am not sure i am ready for that, my experience is shallow and only based on my own RaPi that i 99,99% run headless. On the other hand it would be a very small and space safing concept..and cheap..compared to the use of Laptops (the go to company solution when computers are needed).

It also had the risk that i am the only one that could unfuck anything if things go south..it also has the advantage that i am the only one who could fix things when it goes south...

so much temptation

A year ago I built my first todo, not from a tutorial, but using basic libraries and nw.js, and doing basic dom manipulations.

It had drag n drop, icons, and basic saving and loading. And I was satisfied.

Since then I've been working odd jobs.

And today I've decided to stretch out a bit, and build a basic airtable clone, because I think I can.
And also because I hate anything without an offline option.

First thing I realized was I wasn't about to duplicate all the features of a spreadsheet from scratch. I'd need a base to work from.

I spent about an hour looking.
Core features needed would be trivial serialization or saving/loading.

Proper event support for when a cell, row, or column changed, or was selected. Necessary for triggering validation and serialization/saving.

Custom column types.

Embedding html in cells.

Reorderable columns

Optional but nice to have:

Changeable column width and row height.

Drag and drop on rows and columns.

Right click menu support out of the box.

After that hour I had a few I wanted to test.

And started looking at frameworks to support the SPA aspects.

Both mithril and riot have minimal router support. But theres also a ton of other leightweight frameworks and libraries worthy of prototyping in, solid, marko, svelte, etc.
I didn't want to futz with lots of overhead, babeling/gulping/grunting/webpacking or any complex configuration-over-convention.

Didn't care for dom vs shadow dom. Its a prototype not a startup.

And I didn't care to do it the "right way". Learning curve here was antithesis to experimenting. I was trying to get away from plugin, configuration-over-convention, astronaut architecture, monolithic frameworks, the works.

Could I import the library without five dozen dependancies and learning four different tools before getting to hello world?
"But if you know IJK then its quick to get started!", except I don't, so it won't. I didn't want that.

Could I get cheap component-oriented designs?

Was I managing complex state embedded in a monolith that took over the entire layout and conventions of my code, like the world balanced on the back of a turtle?

Did it obscure the dom and state, and the standard way of doing things or *compliment* those?

As for validation, theres a number of vanilla libraries, one of which treats validation similar to unit testing, which seems kinda novel.

For presentation and backend I could do NW.JS, which would remove some of the complications, by putting everything in one script. Or if I wanted to make it a web backend, and avoid writing it in something that ran like a potato strapped to a nuclear rocket (visual studio), I could skip TS and go with python and quart, an async variation of flask.
This has the advantage that using something thats *not* JS, namely python, for interacting with a proper database, and would allow self-hosting or putting it online so people can share data and access in real time with others.

And because I'm horrible, and do things the wrong way for convenience, I could use tailwind.
Because it pisses people off.

How easy (or hard) would it be to recreate a basic functional clone of the core of airtable?

I don't know, but I have feeling I'm going to find out!

Going through my lore notes. And I'm playing a game with myself, so to speak: it's called "is this metal enough?", but with a side of quasi-metaphysical arcane technobabble plus mass wallmelting and nightmarishly psychedelic confusion.

For example... why are shadow gates a thing? Well, because of the undoing of time caused a multiplicity of parallel cycles that will, inevitably, slowly collapse upon themselves through a sequence of irreducible asynchronicities. But of course!

Now, as for the metal part, that's the undoing of time. You see, the Somberlain attempted to cast the most sinful signa in order to restore the desolate mortal realm as it stood on the brink of a world-ending cataclysm, this was after a decade of brutal, reckless litechnical abuse during the civil war fought amongst the first undecimvirate...

Now, he intended to roll back time itself as a way to avoid the cataclysm and restore life to the mortal realm, but the cost was immense: time was not rolled back, but rather __forcefully__ torn apart; it was effectively shredded, shattered, and undone.

Countless lives were lost as nearly six hundred years of Being were __erased__ in an instant, the most heinous large-scale blood sacrifice in history, spanning the entirety of the lower fragment of reality. I mean is this too dark, I'm not sure. How about I clarify: he didn't just snuff out their lives, no, they CEASED TO EXIST. THEY NEVER EXISTED. GONE. UNBECOMED INTO A TRUE IMMEMORIAL. OVER FIVE CENTURIES OF EVERY CONSCIOUS MOMENT ON EARTH DEVOURED TO FUEL HIS DARK MAGIC.

That's gotta have consequences, right? Well, obviously you'll get temporal distortions after that shit, I mean duh...

But wait, I'm lost, you say the undecimvirate deified themselves but were cast down after the whole superman spinning the earth backwards thing went full bathory and erased entire centuries from the fabric of the cosmos, so they were turned into the eleven thrones to guard over the eleven circles of the night eternal... but how is that linked to natural occurrences of teleportation?

First off, because *natural* teleportation is distinct from *artificial* teleportation. Failed experiments with (and miscasts of) mass transference of living matter are one of the leading causes of death among litarchs. It is not an instant transmission, just very, very quick, moreso than a mortal mind can process, that's why the "dilate" and "delay" sigils are added, so as to make the journey seem slowed down to the perceptions of whomever is teletransported, this is meant to ensure their brains don't __melt__ from the experience.

Similar reason as to why you have to give the _approximate_ total weight to carry when inscribing the ritual circle, you *do* know that it is __highly__ recommended to use accurate weighing scales to approximate this quantity, as under or overestimating it can lead to _FATAL_ consequences... do you not?

No, *natural* occurrences of teleportation do not have these constraints for two reasons: one, because both ends of the gateway are _fixed_ in both time and space due to the logic-defying occurrence of a future event being undeniably the cause of the past it revisited. Put on this toga. They are inextricably linked through the metaphorical and *literal* corpse of infinite collapsed timelines, which generates a conduit through the first circle of the night eternal, which *is* the domain of both forgetfulness and horror immemorial.

Second, the final layer on our stratified reality, that is, the final circle before the INVIOLABLE divine veil, wraps around the night eternal, which is why we call it "the shell". Or "Crisalida" if you dig Luis Alberto. It is a realm entirely outside of time, which is why the patriarchs can grant immortality, you see. By proximity to this sacred shell of existence, the timeline-corpse-conduit that links both ends of a shadow gate is, for all intents and purposes, approaching total chronostasis, therefore making it so bypassing physical space in a few seconds doesn't give you permanent loss of the sense of self as your brain turns into liquified jelly.

I don't remember what I was getting at and I don't care.

So, like, why doesn't Java let me do manual memory management? In C# if I want to screw up the code-base and everyone that comes after me with my half-informed experiments it totally lets me.

So leadership comes and goes but engineers remain, stuck repeating the same tasks over and over. Companies seem to forget their own experiments. How can we force that info to get retained between PMs and leadership?

PM needs experiments running this weekend. One set has a NullPointerException. Just told him to tell me when he's fixed it. He's been painful to work with, that at this point I have no empathy. Just cackling as it's not my problem until Monday! 😂

Mull over the flow and data for days. Write tests first as small experiments to explore the core functionality.

Any ideas for experiments with data from WiFi monitors? Using aircrack-ng / airodump. For IoT themed UGR project