As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

There should be a communist programming language.

- There are no classes.
- There is no inheritance.
- All code is executed simultaneously, since it's equal.
- All variables are global, since everything belongs to everyone
- There are no private functions
- Every function must have side effects, for the 'greater good'
- As soon as it is written, you no longer own the code
- Instead the code owns you
- And your machine

I slowly get why this thing didn't work out on society either.

You know who sucks at developing APIs?

Facebook.

I mean, how are so high paid guys with so great ideas manage to come up with apis THAT shitty?

Let's have a look. They took MVC and invented flux. It was so complicated that there were so many overhyped articles that stated "Flux is just X", "Flux is just Y", and exactly when Redux comes to the stage, flux is forgotten. Nobody uses it anymore.

They took declarative cursors and created Relay, but again, Apollo GraphQL comes and relay just goes away. When i tried just to get started with relay, it seemed so complicated that i just closed the tab. I mean, i get the idea, it's simple yet brilliant, but the api...

Immutable.js. Shitload of fuck. Explain WHY should i mess with shit like getIn(path: Iterable<string | number>): any and class List<T> { push(value: T): this }? Clojurescript offers Om, the React wrapper that works about three times faster! How is it even possible? Clojure's immutable data structures! They're even opensourced as standalone library, Mori js, and api is great! Just use it! Why reinvent the wheel?

It seems like when i just need to develop a simple react app, i should configure webpack (huge fuckload of work by itself) to get hot reload, modern es and jsx to work, then add redux, redux-saga, redux-thunk, react-redux and immutable.js, and if i just want my simple component to communicate with state, i need to define a component, a container, fucking mapStateToProps and mapDispatchToProps, and that's all just for "hello world" to pop out. And make sure you didn't forget to type that this.handler = this.handler.bind(this) for every handler function. Or use ev closure fucked up hack that requires just a bit more webpack tweaks. We haven't even started to communicate to the server! Fuck!

I bet there is savage ass overengineer sitting there at facebook, and he of course knows everything about how good api should look, and he also has huge ass ego and he just allowed to ban everything that he doesn't like. And he just bans everything with good simple api because it "isn't flexible enough".

"React is heavier than preact because we offer isomorphic multiple rendering targets", oh, how hard want i to slap your face, you fuckface. You know what i offered your mom and she agreed?

They even created create-react-app, but state management is still up to you. And react-boierplate is just too complicated.

When i need web app, i type "lein new re-frame", then "lein dev", and boom, live reload server started. No config. Every action is just (dispatch) away, works from any component. State subscription? (subscribe). Isolated side-effects? (reg-fx). Organize files as you want. File size? Around 30k, maybe 60 if you use some clojure libs.

If you don't care about massive market support, just use hyperapp. It's way simpler.

Dear developers, PLEASE, don't forget about api. Take it serious, it's very important. You may even design api first, and only then implement the actual logic. That's even better.

And facebook, sincerelly,

Fuck you.

A very sad side effect from my new job.

When I get home, I can't bear sitting behind a screen for longer than an hour or two.

I really want to keep on programming at home but I just can't put myself to it after work anymore :'(.

I actually feel pretty sad about it 😭

Every time I do a dirty fix and someone in my MR comments "have you investigated the root cause" I wanna kill myself.

No bro, I havent investigated the root cause because this ticket is 3 months old and was passed around like a hot potato from team to team until it got assigned to me.

If you want I can add a comment to refactor this in the future. As far as Im concerned any refactors are out of scope, also I atleast came up with some kind of solution that noone else was able to in 3 months. So im not gonna waste my time on refactoring this piece of shit code under immense pressure from management who thinks it was me who dragged this ticket for 3 months.

Its working, it doesnt cause any side effects, we all gonna die soon and nothing really matters, so fuck off.

Let the student use their own laptops. Even buy them one instead of having computers on site that no one uses for coding but only for some multiple choice tests and to browse Facebook.

Teach them 10 finger typing. (Don't be too strict and allow for personal preferences.)

Teach them text navigation and editing shortcuts. They should be able to scroll per page, jump to the beginning or end of the line or jump word by word. (I am not talking vi bindings or emacs magic.) And no, key repeat is an antifeature.

Teach them VCS before their first group assignment. Let's be honest, VCS means git nowadays. Yet teach them git != GitHub.

Teach git through the command line. They are allowed to use a gui once they aren't afraid to resolve a merge conflict or to rebase their feature branch against master. Just committing and pushing is not enough.

Teach them test-driven development ASAP. You can even give them assignments with a codebase of failing tests and their job is to make them pass in the beginning. Later require them to write tests themselves.

Don't teach the language, teach concepts. (No, if else and for loops aren't concepts you god-damn amateur! That's just syntax!)

When teaching object oriented programming, I'd smack you if do inane examples with vehicles, cars, bikes and a Mercedes Benz. Or animal, cat and dog for that matter. (I came from a self-taught imperative background. Those examples obfuscate more than they help.) Also, inheritance is overrated in oop teachings.

Functional programming concepts should be taught earlier as its concepts of avoiding side effects and pure functions can benefit even oop code bases. (Also great way to introduce testing, as pure functions take certain inputs and produce one output.)

Focus on one language in the beginning, it need not be Java, but don't confuse students with Java, Python and Ruby in their first year. (Bonus point if the language supports both oop and functional programming.)

And for the love of gawd: let them have a strictly typed language. Why would you teach with JavaScript!?

Use industry standards. Notepad, atom and eclipse might be open source and free; yet JetBrains community editions still best them.

For grades, don't your dare demand for them to write code on paper. (Pseudocode is fine.)

Don't let your students play compiler in their heads. It's not their job to know exactly what exception will be thrown by your contrived example. That's the compilers job to complain about. Rather teach them how to find solutions to these errors.

Teach them advanced google searches.

Teach them how to write a issue for a library on GitHub and similar sites.

Teach them how to ask a good stackoverflow question :>

Functional programming jokes don't work because there are no side effects

I think having the wrong job can really bring down the quality of life.

My friend has to drive two hours each way to get to and from work. That's four hours wasted commuting.. and his job is service desk agent.
What are the consequences, you ask? He never has a spare second to talk to me, he's quickly developing gray hairs and he has no time awareness.

Having the wrong job is unhealthy and results in a cascade of bad side effects.. When most of your day involves work-related things, that's just wrong. There is no Yin-Yang there. I know because my work life is somewhat balanced.

TL;DR :

"when i die i want my group project members to lower me into my grave so they can let me down one last time"

STORY TIME

Last year in College, I had two simultaneous projects. Both were semester long projects. One was for a database class an another was for a software engineering class.

As you can guess, the focus of the projects was very different. Databases we made some desktop networked chat application with a user login system and what not in Java. SE we made an app store with an approval system and admin panels and ratings and reviews and all that jazz in Meteor.js.

The DB project we had 4 total people and one of them was someone we'll call Frank. Frank was also in my SE project group. Frank disappeared for several weeks. Not in class, didn't contact us, and at one point the professors didn't know much either. As soon as we noticed it would be an issue, we talked to the professors. Just keeping them in the loop will save you a lot of trouble down the road. I'm assuming there was some medical or family emergency because the professors were very understanding with him once he started coming back to class and they had a chance to talk.

Lesson 1: If you have that guy that doesn't show up or communicate, don't be a jerk to them and communicate with your professor. Also, don't stop trying to contact the rogue partner. Maybe they'll come around sometime.

It sucked to lose 25% of our team for a project, but Frank appreciated that we didn't totally ignore him and throw him under the bus to the point that the last day of class he came up to me and said, "hey, open your book bag and bring it next to mine." He then threw a LARGE bottle of booze in there as a thank you.

Lesson 2: Treat humans as humans. Things go wrong and understanding that will get you a lot farther with people than trying to make them feel terrible about something that may have been out of their control.

Our DB project went really well. We got an A, we demoed, it worked, it was cool. The biggest problem is I was the only person that had taken a networking class so I ended up doing a large portion of the work. I wish I had taken other people's skills into account when we were deciding on a project. Especially because the only requirement was that it needed to have a minimum of 5 tables and we had to use some SQL language (aka, we couldn't use no-SQL).

The SE project had Frank and a music major who wanted to minor in CS (and then 3 other regular CS students aside from me). This assignment was make an app store using any technology you want. But, you had to use agile sprints. So we had weekly meetings with the "customer" (the TA), who would change requirements on us to keep us on our toes and tell us what they wanted done as a priority for the next meeting. Seriously, just like real life. It was so much fun trying to stay ahead of that.

So we met up and tried to decided what to use. One kid said Java because we all had it for school. The big issue is trying to make a Java web app is a pain in the ass. Seriously, there are so many better things to use. Other teams decided to use Django because they all wanted to learn Python. I suggested why not use something with a nice package system to minimize duplicating work that had already been done and tested by someone. Kid 1 didn't like that because he said in the real world you have to make your own software and not use packages. Little did he know that I had worked in SE for a few years already and knew damn well that every good project has code from somewhere else that has already solved a problem you're facing. We went with Java the first week. It failed miserably. Nobody could get the server set up on their computers. Using VCS with it required you to keep the repo outside of the where you wrote code and copy and paste changes in there. It was just a huge flop so everyone else voted to change.

Lesson 3: Be flexible. Be open to learning new things. Don't be afraid to try something new. It'll make you a better developer in the long run.

So we ended up using Meteor. Why? We all figured we could pick up javascript super easy.Two of us already knew it. And the real time thing would make for some cool effects when an app got a approved or a comment was made. We got to work and the one kid was still pissed. I just checked the repo and the only thing he committed was fixing the spelling of on word in the readme.

We sat down one day and worked for 4 straight hours. We finished the whole project in that time. While other teams were figuring out how to layout their homepage, we had a working user system and admin page and everything. Our TA was trying to throw us for loops by asking for crazy things and we still came through. We had tests that ran along side the application as you used it. It was friggin cool.

Lesson 4: If possible, pick the right tool for the job. Not the tool you know. Everything in CS has a purpose. If you use it for its purpose, you will save days off of a project.

"I'm almost done, I'll just need to add tests!"

Booom! You did it, that was a nuke going off in my head.

No, you shouldn't just need to add tests. The tests should have been written from the get go! You most likely won't cover all the cases. You won't know if adding the tests will break your feature, as you had none, as you refactor your untested mess in order to make your code testable.

When reading your mess of a test case and the painful mocking process you went through, I silently cry out into the void: "Why oh why!? All of this suffering could have been avoided!"

Since most of the time, your mocking pain boils down to not understanding what your "unit" in your "unit test" should be.

So let it be said:

- If you want to build a parser for an XML file, then just write a function / class whose *only* purpose is: parse the XML file, return a value object. That's it. Nothing more, nothing less.
- If you want to build a parser for an XML file, it MUST NOT: download a zip, extract that zip, merge all those files to one big file, parse that big file, talk to some other random APIs as a side-effect, and then return a value object.

Because then you suddenly have to mock away a http service and deal with zip files in your test cases.

The http util of your programming language will most likely work. Your unzip library will most likely work. So just assume it working. There are valid use cases where you want to make sure you acutally send a request and get a response, yet I am talking unit test here only.

In the scope of a class, keep the public methods to a reasonable minimum. As for each public method you shall at least create one test case. If you ever have the feeling "I want to test that private method" replace that statement in your head with: "I should extract that functionality to a new class where that method public. I then can create a unit test case a for that." That new service then becomes a dependency in your current service. Problem solved.

Also, mocking away dependencies should a simple process. If your mocking process fills half the screen, your test setup is overly complicated and your class is doing too much.

That's why I currently dig functional programming so much. When you build pure functions without side effects, unit tests are easy to write. Yet you can apply pure functions to OOP as well (to a degree). Embrace immutability.

Sidenote:

It's really not helpful that a lot of developers don't understand the difference between unit, functional acceptance, integration testing. Then they wonder why they can't test something easily, write overly complex test cases, until someone points out to them: No, in the scope of unit tests, we don't need to test our persistance layer. We just assume that it works. We should only test our businsess logic. You know: "Assuming that I get that response from the database, I expect that to happen." You don't need a test db, make a real query against that, in order to test that. (That still is a valid thing to do. Yet not in the scope of unit tests.)

New country, new company, new team, new projects.
I'm supposed to be the TL of a team working on a React project.

A guy in his late 40s celebrates himself as "the senior", he basically just finished watching a youtube thing, React 101 crash course or similar. The other two juniors who did only Wordpress so far venerate him like a god.

The code, of course, is one on the finest pieces of crap I ever had the pleasure to deal with in my life: naturally a bunch of JQuery plugins for everything, no tests, no state management, side effects everywhere, shared state and globals like hell, everything written in ES3/ES5 style, no types, no docs, build and deploy totally manual, deep props drilling at every level... and not to mention the console.log() shipped in prod.

First day, already headache.
Full rewrite start tomorrow.
Hiring real devs as well.

I'm scared like a kid!
Next week , I'm getting my new medicine as a serum which is full of side effects : fever , headache , ...
And because bradicardia is one of them (several people died cause of this !) , I must be in the hospital under observation for 24h (actually 24h coding ) .

Hey i know it's stupid !
I know even if my heart stops beating i won't die in hospital (i hope so)
And i'm not a nervous guy!
I'm getting back to my code maybe that helps 😸

Realizing that the former so-called PHP developers based the entirety of their so-called dashboard framework (self-written of course) on GET requests.

Every. Controller. Only. Accepts. Get. Requests.

It creates stuff? So what! It does update? No matter! It deletes? Who cares!

Just call that URL, and it will release all hell, plagued with multiple side-effects, and then issue a redirect.

Of course that one delete button was inside some twitter bootstrap tabs, and due to the redirect the page always reloaded and the content manager landed on a very different tab. Meaning if they wanted to delete multiple records, they had to hit "activate tab" and "delete" and "activate tab" and "delete" -- rinse and repeat.

It's our *job* to make things easier for our users! Not to waste their time. (Unless you are browser game developer. Then do your thing.)

And we are talking basic CRUD! Basic CRUD! I am not even demanding for it to be restful or to have some parts of a HTML page being updated on the fly with such rad and new technologies like ajax!

There is just question I would like to ask whoever build this: Seriously!?

TL;DR: At a house party, on my Phone, via shitty German mobile network using the GitLab website's plain text editor. Thanks to CI/CD my changes to the code were easily tested and deployed to the server.

It was for a college project and someone had a bug in his 600+ lines function that was nested like hell. At least 7 levels deep. Told him before I went to that party it's probably a redefined counter variable but he wouldn't have it as he was sure it was an error with the business logic. Told him to simplify the code then but he wouldn't do that either because "the code/logic is too complex to be simplified"... Yeah... what a dipshit...
Nonetheless I went to the party and He kept debugging. At some point he called me and asked me to help him the following day. Knowing that the code had to be fixed anyways I agreed.
I also knew I wouldn't be much of a help the next day due to side effects of the party, so I tried looking at this shitshow of a function on my phone. Oh did I mention it was PHP, yet? Yeah... About 30 minutes and a beer later I found the bug and of course it was a redefined counter variable... My respect for him as a dev was already crumbling but it died completely during that evening

While messing around with the Windows WM_NCPAINT message, I forced the WindowProc to return without calling DefWindowProc.

This resulted in interesting effects when pressing mouse buttons down on the right hand side of the title bar. This is on Windows 10.

Bottom part of the image is when I clicked on things and is Windows 9x-XP style. Top part of the image is when the window was deactivated and is Vista/Windows 7 style. Once they appear, the buttons behave as they did (visually - e.g. highlighting) as they did on those versions of Windows.

Just found it funny to see older bits of the Windows UI still hanging around behind the scenes!

“Dear Manager, the reason I didn’t complete my sprint task today was that while I was nursing my fiancé’s COVID vaccine severe side effects, said fiancé’s Chinese roommate put a jar of some fermented product called “Golden Smell” in a precarious place from which I broke it, causing a veritable golden shower of glass shards and odors to permeate the workspace. If you don’t hear from me by standup, tell my mom i’m sorry."

FUCK ALL THOSE MONKEYS THAT WROTE ALL THE SHITTY CODE WHICH I'VE SPENT THE MAJORITY OF MY DAYS HAVING TO FIGURE OUT WHAT THE SHIT IT DOES AND WHY I CAN'T JUST BURN IT....

AND WHY THE FUCK DO BUSINESS USERS SEEM TO THINK THAT DEVELOPERS CAN UNDERSTAND ALL THEIR BUSINESS TALK...

IF I UNDERSTAND ALL OF WHAT YOU DO, YOU WILL BE OUT OF A JOB....

P.S. APPARENTLY ONE OF MY MEDS SIDE EFFECTS ARE INCREASED IRRATIBILTY. THE SLIGHTEST ANNOYANCES NOW PISS ME OFF...

SO APPARENTLY THAT MEANS I HAVE A FREE LICENSE TO BLOW UP N RANT ON THE JOB RIGHT?

... 🖕

Saw this today in the exercise code of a deep learning lecture. These people are doing their PhDs in deep learning 😳

* the snippet has no side effects

There was a sales manager who was raked with overseeing me and another dev finish a last minute request project. He said at one point to the other dev that he was mad at developers because we understood something that he would never understand.

This same manager would often sit in on estimation meetings and constantly say that we were estimating too high and needed to come up with faster solutions. When we would offer him with caveats of possible technical debt or unintended side-effects/performance issues, he'd want us to go with that solution. He would then complain that we were always wanting to work on technical debt and that our application was slow. He would also ask for very high level estimates for large, unscoped features/apps without any meaningful level of detail, then hold us to the high-level estimated date even after revealing additional features previously unmentioned.

We learned to never compromise on the right solution and to push back hard on dates without proper scoping. They didn't learn, so I and most of the good devs left.

Me: Can you tell me how to do X?
ChatGPT: yes, you can do xwz!
Me: I researched your suggestion and every source I find mentions that you should not do it because it would mess with the UI thread, amongst other side effects.
ChatGPT: Yes, you should not do xwz.

I’m kinda liking this thing, it’s full of noob traps.

I was laid off. The reason? Well, they didn't really want to say but they were clear it wasn't due to performance. (Thankfully, I got severence pay.) From my perspective it really came out of nowhere, no warnings or even hints that this was coming, which has me spinning. 😵 If I'm doing well at my job and the company is doing well, how in the seven hells could I get laid off??

What they said was partly the reason didn't seem true, or not the whole truth. They essentially stated that "they talked with everyone I worked with" (probably not true based on their decision, but who knows) and came to the conclusion I wasn't suitable to work on large teams, and that's the direction they are moving in. As if it wasn't something that could be improved on 🤔

I'll be the first to admit I'm not the best communicator face-to-face, mainly due to my social anxiety but also because I have too many thoughts. It can be difficult to condense them down for other people in the heat of the moment. (I'm an INTP, if that helps you to understand what I mean.) However, I know I'm a pretty good communicator overall since I listen and pay special attention to phrasing and word choice. So most people I worked with there seemed quite satisfied with communication with me. There were only 2-3 out of more than 12 who I had any difficulty working with.

So why did I have trouble properly working with a couple people? I hesitate to say this but, like other jobs I've had, well... they didn't have either the experience or knowledge to understand me. Basically, they were stupid. I was pretty frustrated working with such inadequately prepared people on a complex project with ludicrously short deadlines, and had no desire to work overtime so I could educate or guide them.

To give perspective, one React developer didn't understand how object properties work with JavaScript. 🤦‍♀️ (They are references, by the way. And yes you can have an object reference inside another object!) Another React developer thought it was okay to have side effects during the render lifestyle because they didn't affect the component itself, even if it was a state change in a parent component. 🤦‍♀️🤦‍♀️

So what is the real reason I lost my job, if not performance? Could be I pissed off the stupid (and loud) ones which hurt my reputation. My main theory, however, is that I was raising the cost of the company's healthcare. I had a diseased organ so I did miss some work or worked from home more than I should have, and used my very good health insurance to the fullest extent I could. Of course, if they say that's the reason then they can get sued.

Huge bummer, whatever the case. I definitely learned some lessons from this situation that others in a similar position could find useful. I can write that up if anyone expresses interest.

Honestly though, this is a good thing in the end, because I was already planning to leave in a month or 2 once I found a better job. I was waiting for the right time for the project I was on and for my own financial stability. So I'm trying hard not to let this affect my self-esteem and think of it as an opportunity to get my dream job, which is working with a remote-first company that is focused on improving the human condition.

Being unemployed isn't ideal, but at least I didn't have to quit! And I get to have a bit of a vacation of a sort.

I just came out of over 4 weeks of loneliness with no real life face to face interaction at all because of lockdown. The only time I saw another human being was when I went to the grocery store, but they were strangers.

Last few days, I started experiencing the side effects of having no real life social interaction.

My throat was getting constrained, it felt I had many things to speak and everything is stuck in throat. It felt as if my throat was choking me. I was feeling very stressed. It brought the flashbacks of the time when I was seriously depressed. I couldn't really sleep last night

Today, I decided to visit my close relatives, the place where I grew up, the place I find as my heaven on earth and I feel so much better just being in the presence of people who know me, whom I know since I born.

I don't know if anyone here experienced similar feelings. I wanted to share it here.

I dislike the damage web development tools have done to my programming habits.

The rapid feedback provided from the development environment (e.g. hot-reloads) encourages me to constantly bang out code with very little consideration for its side-effects.

This tendency has become a handicap when I write instructions for hardware with much less resources, such as a microcontroller.

When I was in 11th class, my school got a new setup for the school PCs. Instead of just resetting them every time they are shut down (to a state in which it contained a virus, great) and having shared files on a network drive (where everyone could delete anything), they used iServ. Apparently many schools started using that around that time, I heard many bad things about it, not only from my school.
Since school is sh*t and I had nothing better to do in computer class (they never taught us anything new anyway), I experimented with it. My main target was the storage limit. Logins on the school PCs were made with domain accounts, which also logged you in with the iServ account, then the user folder was synchronised with the iServ server. The storage limit there was given as 200MB or something of that order. To have some dummy files, I downloaded every program from portableapps.com, that was an easy way to get a lot of data without much manual effort. Then I copied that folder, which was located on the desktop, and pasted it onto the desktop. Then I took all of that and duplicated it again. And again and again and again... I watched the amount increate, 170MB, 180, 190, 200, I got a mail saying that my storage is full, 210, 220, 230, ... It just kept filling up with absolutely zero consequences.
At some point I started using the web interface to copy the files, which had even more interesting side effects: Apparently, while the server was copying huge amounts of files to itself, nobody in the entire iServ system could log in, neither on the web interface, nor on the PCs. But I didn't notice that at first, I thought just my account was busy and of course I didn't expect it to be this badly programmed that a single copy operation could lock the entire system. I was told later, but at that point the headmaster had already called in someone from the actual police, because they thought I had hacked into whatever. He basically said "don't do again pls" and left again. In the meantime, a teacher had told me to delete the files until a certain date, but he locked my account way earlier so that I couldn't even do it.
Btw, I now own a Minecraft account of which I can never change the security questions or reset the password, because the mail address doesn't exist anymore and I have no more contact to the person who gave it to me. I got that account as a price because I made the best program in a project week about Java, which greatly showed how much the computer classes helped the students learn programming: Of the ~20 students, only one other person actually had a program at the end of the challenge and it was something like hello world. I had translated a TI Basic program for approximating fractions from decimal numbers to Java.
The big irony about sending the police to me as the 1337_h4x0r: A classmate actually tried to hack into the server. He even managed to make it send a mail from someone else's account, as far as I know. And he found a way to put a file into any account, which he shortly considered to use to put a shutdown command into autostart. But of course, I must be the great hacker.

I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...

Example
Controller -> Business/Application Logic -> Infrastructure Layer

(shortened)

Now in the infrastructure layer we have a cache that caches an http rest call to another service.

One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.

The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.

Today Gizmo presented a new solution.

The solution was to log and swallow all exceptions and just return null everywhere.

Yay... Gizmo. You won the Oscar for bad choices TM.

Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.

so, flexbox.

and my only question is: why did it take CSS 30 years to get the features which it should have had from the start? now because of that, even this awesome thing is messy due to how the old features collide (or don't collide, i'm not entirely sure tbh) with it.

but maan, flexbox! now at least a part of css feels like a tool made to solve the problem it's supposed to solve, instead of layers of hacks that you can somehow hack into having the side effects which result in it doing what you want it to do!

Why is it that virtually all new languages in the last 25 years or so have a C-like syntax?

- Java wanted to sort-of knock off C++.
- C# wanted to be Java but on Microsoft's proprietary stack instead of SUN's (now Oracle's).
- Several other languages such as Vala, Scala, Swift, etc. do only careful evolution, seemingly so as to not alienate the devs used to previous C-like languages.
- Not to speak of everyone's favourite enemy, JavaScript…
- Then there is ReasonML which is basically an alternate, more C-like, syntax for OCaml, and is then compiled to JavaScript.

Now we're slowly arriving at the meat of this rant: back when I started university, the first semester programming lecture used Scheme, and provided a fine introduction to (functional) programming. Scheme, like other variants of Lisp, is a fine language, very flexible, code is data, data is code, but you get somewhat lost in a sea of parentheses, probably worse than the C-like languages' salad of curly braces. But it was a refreshing change from the likes of C, C++, and Java in terms of approach.

But the real enlightenment came when I read through Okasaki's paper on purely functional data structures. The author uses Standard ML in the paper, and after the initial shock (because it's different than most everything else I had seen), and getting used to the notation, I loved the crisp clarity it brings with almost no ceremony at all!

After looking around a bit, I found that nobody seems to use SML anymore, but there are viable alternatives, depending on your taste:

- Pragmatic programmers can use OCaml, which has immutability by default, and tries to guide the programmer to a functional programming mindset, but can accommodate imperative constructs easily when necessary.
- F# was born as OCaml on .NET but has now evolved into its own great thing with many upsides and very few downsides; I recommend every C# developer should give it a try.
- Somewhat more extreme is Haskell, with its ideology of pure functions and lazy evaluation that makes introducing side effects, I/O, and other imperative constructs rather a pain in the arse, and not quite my piece of cake, but learning it can still help you be a better programmer in whatever language you use on a day-to-day basis.

Anyway, the point is that after working with several of these languages developed out of the original Meta Language, it baffles me how anyone can be happy being a curly-braces-language developer without craving something more succinct and to-the-point. Especially when it comes to JavaScript: all the above mentioned ML-like languages can be compiled to JavaScript, so developing directly in JavaScript should hardly be a necessity.

Obviously these curly-braces languages will still be needed for a long time coming, legacy systems and all—just look at COBOL—, but my point stands.

Personal update:
So i have been to psychiatrist few days ago. I got a prescription for anti depression drugs and today is the 4th day of my therapy. I feel a bit better. At least i can sleep can focus on things. Unfourtanetly mentaly i dont feel better. That rant that i wrote before didnt help me neither (i deleted it). That drug that im taking has a shit ton of possible side effects uncluding anger. My massive untrust to people dosent help neither.

To anybody who didnt read the previous rant. I have meet a classmate that had a idea for a android app. I have fought he is one of that bad, stupid kind. I was wrong i said bad things to him but eventualy i helped him by showing where he can get help with the app.

I shouldnt have responded to him in the first place. Now i feel bad. I have no idea how you are going to respond im scared. I prejudged him but im now sorry. I have no idea how my life is going to go.

I also have tried applying for a awesome C# internship, perfect for a student: paid and might get experience in C#. I have send them 2 emails on the address that they gave me during open days (where i had talked with HR and devs personaly about their job) and i got no responce since last month...

Finals for the first semester are closing in as well. I dont know if im going to pass or not. And that is the worst thing i have to worry about now.

If you ever think of using React Native, don't

Save yourself the trauma of endless build errors and indeterministic side effects

Run for your fucking life and never touch that shit

Fuck Ajax and it's stupid fucking side effects. A language should not have inherent side effects. "Oh, you like responsiveness?! How about I just remove all your events after a post?! How about that for responsive design ya lil bitch!"

Not really a rant (?)

I started my first programming job in January this year. I went there staight after Highschool, so i had no real experience, knew only the basics of software development and my written code was quite a mess. So one of my first real tasks (after 2 months) was to write a business logic for batch handling (for a warehouse management system). I invested quite some time to develop a suitable architecture, talked with some other developers and wanted to cover the whole thing with unit tests (which really nobody at the company uses). So I spent about 3 weeks to write the whole thing, test it and improve it many times. It worked perfectly and I got pretty good feedback from the code-review.

1 month ago - the code worked perfectly and was multiple times testet (also by the client) - the client came with some totally new requirements for the batch handling. I tried to impelemt them, but soon found out, that the architecture doesn't supported them, it was not build for the required handling and would soon become a totally mess, if i tried to make it work.

So I was pretty mad, because I had to change the whole fucking thing, but I also wanted to make it better. I hab gained some experience and decided (with some help of a senior dev) to make a completely new try with a different architecture, that can be easily expanded, if needed. I build my concept, wrote and tested the whole new code in 3 days. Fucking 3 days compared to the initial 3 weeks, and it worked, better and even faster.

I was quite pissed to delete the old code, and especially that i had wasted 3 weeks for it and had to struggle with many different things. But I lerarned so much from it and also in the months between, that I was also really glad that I had the opportiunity to write it again.

This whole thing made me now realize that this is, what I really like to do and what I'm good in. I really enjoy learning new things and for me, programming is the best and easiest way to do it. Despite alle the cons and annoying side effects of it, I really found my dream job here.

Being addicted to Linux is a side effect of me not being able to get a faster computer when I was young.. Windows had a hard time on the machine I had.. Meanwhile Linux Desktop with compiz fusion ran like lightning with all those crazy effects.. If I had a faster computer I think I would've rather be addicted to AAA games.. Nowadays I can't use Windows because it's not as user friendly as things like Gnome.. Also it's not developer friendly compared to Linux Distros.. Simple things like changing the volume feels clunky in windows.. And the shitty windows explorer is the worst file manager of all the default ones in any OS.

This is a story about my disappointment in modern GUI editors for desktop applications.

Well, first of all, I grew up with Delphi 5. Delphi has an awesome form editor. It's intuitive and works without any problem. It always does what you want it to do. Prototyping is really a problem of seconds here, even for people that never used it (I guess).

But the problem is that it is Delphi. Its so old, bloated, and most problems you'll ever have have been solved (through a hack) 20 years ago in some weird forum.

So I looked on and tried many other drag'n'drop gui editors.

The one for java is the biggest pile of crap I've ever seen. It slows down eclipse /intellij and does almost never do what I want. At least its not really intuitive.

Right after that, the one for C# (this xml Designer ) is okay-ish, but it's also not really intuitive and does not always what the user wants.

I also tried other ones. But I still miss an intuitive one that works without weird side effects.

I now can understand why the Web dev stack grows in the region of desktop apps. I can prototype stuff even faster in angular than in Delphi.
But shouldn't we improve the desktop stack instead of taking some bloated stack using a language that should have never existed?

Are you planning on entering politics?

Because your documentation is dishonest, doesn't mention side effects and is not meant to be read humans workout a law degree.
Your code on the other hand makes me question whether you try to troll us or whether you are actually unable to understand what you were supposed to do.

What got you into programming?

For me, it were the games. I was and still am amazed by how games work, from one side of the planet to the other side, how good the visual effects are...

!rant
<no trolls tag>

I suffer with anxiety.
I took pills (pristiq), but side effects almost ended with my marriage.
And now I'm having more problems. Even a message from my boss trigger me and I can't think properly.
I have a good job and small mini projects and I enjoy playing games

How do you deal with anxiety?

I told you fucking moron clients doing that "little" change would be complicated and in the worst case it would end fucking up your whole spaghetti crap. A really HUGE spaghetti monster of that you aren't aware because you guys don't know a shit about coding conventions.

*Clients call me complaining about their software is broken*

-Hey, we're in serious trouble. Our users aren't being able to see the proper calculated values. Why that little change had so much side effects?
- I already told you why.
- Can you fix it asap? Our clients are complaining.
- No. Deploy an old copy of the affected modules while you give me a prudent time to refactorize that crap.
- Refactorize?
- ...

I used to work in their place, 3 years later I quit that crappy job and decided to make them my clients. I escaped from the micromanaging thing but I didn't from their ugly practices.

Anyways, I have to fix this shit asap. Money talks, at least until I can find a better client.

Just imagine sicknesses spreading through internet.

I mean real human sicknesses. Of course your laptop can’t generate aids, but hey, did you ever have a song stuck in your head, repeated infinitely? Memes, viral videos, modern pop music, it looks just like perfect delivery mechanisms.

Human brain is flawed and buggy, vulnerable to countless things like optical illusions, uncanny valley, nlp and others. It’s obvious that there is some audiovisual input sequence that may have arbitrary side effects.

We are towards invention of some precisely formed pieces of information that’ll damage your brain forever, maybe drive you insane so there’ll be no way back. Delivered via viral media straight to your brain, destroying it irreversibly.

Be ready to face the future.

Why the hell am I so talkative!!!!!
I think it's better I work alone so that I be less of an annoy for others...
Side-effects of me working at day time..
Missing working at night time all alone..

I dream about discovering weird side effects on certain built-in functions way too often.
I usually implement those myself but without side effects. All in the dream.

Lead: alright people what are your ideas and updates for this page refactor we've been talking about.

dipshit: Alright guys, I've done a quick awesome prototype that I really like...

dipshit: *starts to speak super fast* (I catch words about function composition, clean, no side effects, speed, efficiency. Basically a string of brogrammer buzzwords.)

me: what did you mean by that? How does it work?

dipshit: *basically repeats the same drivel*

me: uh..ok I don't quite understand

everyone else looks confused.

me: ok since you've done a prototype, we take a look at it later

*** After meeting, looks at code ***

It was COMPLETE GARBAGE. He used 1,500+ lines of js in 17 files to make what was essentially a simple 2 item list.

We were looking at a way to overhaul the entire page, he "refactored" maybe perhaps 5% of the page.

There was absolutely nothing clean / functional / composable about this monstrosity. It was as if he read chapter 1 of a book on functional programming and decided he understood enough to call himself an expert.

WHY THE FUCK ARE YOU STILL HIRED?

HOW DO YOU CALL YOURSELF A DEVELOPER?

YOU ARE SELF TAUGHT, DISS PEOPLE WITH FORMAL CS/CE DEGREES AND YOU PRODUCE TRASH CODE?!

ARE YOU SO RETARDED THAT YOU DO NOT RECOGNIZE HOW STUPID YOU ARE?

Please die in a fire, along with your jock attitude and unprofessionalism. Take this worthless junk unfit to be called code with you.

Went bug hunting only to land in a controller method that's 125+ lines long, riddled with side effects, and.... no tests!

There was a big hairy ball of SW mud from another project that a poor coworker had to "reuse". Only that it was impossible because there was no documentation, shit was partly auto-generated with mysterious Excel tables, and the actual code was just as bad. No APIs and nothing, just hacking shit into globals, several nested state machines that were overriding each other's states, and with global side effects. WTF.

Two devs took a look at it - minimum 8 weeks. Schedule was some days, and PM insisted that it was "already working". But the worst thing was that the dev in charge had been looking for another job anyway and quit, so the whole clusterfuck suddenly was on my desk.

The code was so awful that I could only bear it with both eyes closed, so I instead read the spec of this project closely. Turned out that it didn't actually demand this feature, only a small subset of what the ball of mud was supposed to achieve - which I was able to implement from scratch within a day, plus another one for documentation. Phew.

To feel great, to shine professionally, to ride ma bike, to have a healthy family.

Other bonuses are just side effects.

I struggled with weather to post this but I feel like I have to. I didnt want to feed into the fear or give 'them' any more reason to argue against common sense but I guess it cant be helped.

The reason I was gone for a while was because I went and got my vaccination.

In less than half hour after getting the vaccine, I was in the ICU. The staff told me I had a stroke possibly from clotting and inflamation. I couldnt feel my arm or anything below my shoulders. Yes really.

Apparently I "died" for a little while and when they brought me back I was in a coma for almost a week.

I'm back home now and I still dont fully understand what happened. Still have numbness, and horrible headaches, and can barely think straight sometimes, but the doctors told me that I didnt suffer any permanent brain damage according to my scans.

Also they told me I had old damage to my left and right temporal lobe, which makes sense because I have always suffered problems with short term memory and other issues.

And I'm just at a loss how this could happen. I have no serious injuries. We were told this is safe.

And this is the exact reason I didnt want to post it, because now tards will come in and be "lololol serves you right vaxxer!"

If I knew the side effects were this bad maybe I would have changed my mind but no one told me! I mean I think I still would have got it because we have to protect vulnerable people, but still.

The hospital assured me it wasnt the vaccine and must have been an underlaying condition, but I'm not so sure. I just happen to have a pre-existing problem that I dont know about that causes a stroke and paralysis only half an hour after the shot?

And now I dont know if I'll ever be ok. And doctors warned me I may suffer more strokes and to avoid physically demanding tasks for a while. My primary job is construction (not by chooce). Now I face the prospect of not even being able to work my existing job or do the things I love, like hiking, anymore. So much of the world doesnt make any sense right now and I just dont know what to believe anymore.

Tards will probably be in shortly to suggest I check for microchips or test fucking magnets on myself.

No, just stop.

How do you cope with loneliness ?

Mounjaro side effects are kicking my ass. Second week somehow worse than the first week.

First week, day after shot was the worst. Had really bad nausea and only managed to eat 10 saltines. All day.

Second week, two days after shot, woke up just in time to go to the bathroom and projectile vomit (making me acutely aware of the fact that I haven’t puked in *years*). Took that day and the next off work.

Now I’m feeling a lot better on the puke/nausea front, but constipated as heck, desperately hoping that that resolves soon, and going back to work.

But self-reflections are due.

Y’all don’t know how much I hate writing self-reflections.

But I’ve lost almost a pound a day the last 10 days, so … yay?

Pet peeve: the claim that static typing prevents errors.

Today I worked on a C# project that's a mess of nulls, side-effects, inferences, and race conditions. Then I went back to a JS project that's twice the size but written in a clean, well-tested, FP style and currently has fewer than 10 issues logged.

Look, I get that there are upsides to static typing, and I'm open to introducing typescript or flow for our JS code.

I just can't stand the faux-concern from the static typing dingleberries when they are the ones who produce these horrendous lumps of unmaintainable shit, and the JS/Python/Ruby/etc people are over here quietly reinventing functional programming and code modularity.

Starting to learn Haskell/type theory. I have put it off long enough and I hope this time I can get past the 5 minute intro/overview.

So far the only functional programming I have done is trying to write/use functions that take state in parameters only and limiting side effects (that I know of).
Expecting to have my mind blown and to get a monocle too.

On This Episode of Ghetto Medium..

Posted after midnight for extra spooky effects. Read in the dark at your own risk. You've been warned.

So my mother has been on a binge watching shows like long island medium (apparently the taller your hair the closer you are to god or something), and every time we talk she begins at length to talk about, you guessed it.. 'ghosts.'

Now don't get me wrong, I've had some 'spooby' shit occur in my lifetime, the sort that will tighten your sphincter faster than bill cosby asking you if you want some koolaid or grape drank, but I digress.

The ghost talk is tiring. Lately theres been a *flood* of these new shows, purportedly showing mediums and people who can 'look into the other side' and I realize just how vapid and ridiculous it's all become, as if they all are being personally haunted by the ghost of John Edwards burnt out husk of a career. Theres long island beehive big-hair medium, celebrity medium, allison DuBois (the inspiration for that one sappy show *medium*) whos red hair and vacant stare speak of glimpses into centuries past like an intimate unseen horizon. or maybe she forgot to unplug her curling iron in a hotel one time and has been rendered permanently catatonic. And who can forget *Beyond With James Van Praagh* (everyone) whos face, as measured by the width of his mustache, appears to be expanding at a constant rate like a bad image macro edit thats been memed and repasted a thousand times. Then theres Chip Coffee, whos name is about as believable as his teaching degree on the show *Psychic Kids* where he mentored, again, you guessed it, *psychic kids*. Of course theres Tyler Henry, a youthful, uh, "flamboyant" medium for celebrities with ghost problems. Never trust a man with two names, this ones no exception, he looks so clean cut hes either secretly mormon, or secretly gay, maybe both. I'm not judging, but I am saying if I ever saw his clean cut, smooth, wrinkless (seriously, how tyler? how?), all american face, say smiling that subtle smile outside my kitchen sliding glass door at 3 am, his face watching me from the pitch dark outside, I wouldn't at all be surprised, except for the hospital bill I'd have to pay after shitting a brick and needing anal surgery.

At this rate we have mediums popping out left and right, like clowns at one of them R.L Stein nightmare carnivals, or beggers outside a methodone clinic. Geez, they're coming out the wood work, like those painting you see with hidden faces in them, or wheres-waldo posters, only you're trying to find the non-waldo guy amongst all the characters because they're ALL waldo: goofy acting, goofy dressing, and just all around goofy looking.

At this rate I'm fully expecting "pet medium" (starring a character named Stephen King and his marital problems, played by johnny depp eating way to much corn), and "haunted objects medium", and "car medium" (it's just seinfeld in a car, talking to psychics instead of other people), and "ghetto medium."

Today on this episode of "Ghetto Medium"..

Medium: Teneesha, aw yeah girl, u *definitely* ded gurl, uh huh! You WAY to white too be alive, you done passed over gurl!

And in the next episode of Ghetto Medium, one man claims "every time I bend over I can hear "wOoOoOoOoO!, Is my asshole possessed? Find out is it real or fake, and what our verdict is in Ghost Medium, episode 3: A Haunting In My Nether-regions."

Cut commercial break.

"Jerry Springer: One women asks, 'jerry, is my unborn child's foreskin haunted? And later today we ask the crowd, would you have sex with a ghost?"

Welcome to American television 'programming' in 2019.

Yes, it's all brainwashing.

Trying to learn Haskell for the Nth time and the only side effects it has is on my life :/

I would start with the development of the idea me and my friends made a business plan about a while back. It was about a medicine cabinet which offers you only the medication you need and the right amount of it. It furthermore informs you about side effects and alerts when you run out of stock. It was meant to fit elderly as well as also large scale hospitals were one case would be used for each room of patients.

I have a few side project ideas. I started one of them a few months ago (project setup, dependencies, git repo, index page, very basic API and client functionality). But I cannot get myself to work on it or even think about it (for months now). The reason? I do not want to work on the client/frontend! I do not want to deal with React or Vue or Svelte or fuckjs or even jquery. It's a fucking mess.

For the backend, the requests are stateless: you get a request, handle it, and respond back. Need to update state? Database. That's it!
For the frontend, there's just tooo many states I can't keep up with! When the user checks or unchecks this checkbox, I need to maintain the state of the checkbox and maintain the all effects of changing the checkbox while syncing with the backend and making sure the elements are still styled correctly with the applied effects. Multiply that with all the expected interactive elements on the page. It's exhausting!

React Native testing is hair pulling.

Every test needs to have 100 different mocks in place and there are: 3 different methods to mock a function (mock, mockImplementation, and fn), 3 different types of query methods to get elements (get, find, and query), and 5 different selectors to query on (accessibility label, testId, accessibility hint, accessibility value, etc.)

And after reading all this, being diligent and learning the difference between stupid, synonymously-named functions which have wildly different side effects like "getByA11yHint" and "findByA11yHint" (ugh...), after all that, you write out a test with all the appropriate mocks and you want to do something simple and it beats you up all over again.

Button enabled or button disabled. Simple right? Logically the former is "expect(elem).toBeEnabled()" and the latter is "expect(elem).not.toBeEnabled()", right?

Wrong! You're an imbecile. Your tests will fail and never tell you that ".not.toBeEnabled()" and ".toBeDisabled()" don't do the same thing even though they look and sound exactly the same. Only the latter will work. The former makes all your tests fail. Where is this written in the docs? Nowhere?! Great!

👌😄🔫

Oracle database with PL/SQL, heavy use of triggers, and viewception.

Sure, let's take what's supposed to be a data store, embed shitloads of logic in it, make sure everything has side effects, and ensure nothing is ever straightforward.

Untracable, impossible to debug and overall a mess of epic proportions!

Related to queueing theory...

Suburban traffic at a stop lights has developed a tendency to include invisible cars.

You can see where these invisible cars are by the gap between the front bumper of one car the back bumper of the next. Sometimes there is an invisible motorcycle, sometimes there is an invisible semi-tractor trailer. It is becoming an epidemic.

The dumbasses in traffic who do this are usually texting behind the wheel while stopped and they are not always Buffy the ding dong cheerleader nor Sally the Soccer Mom... Suits too... It seems to have gotten worse with pot becoming legal I just realized...

But to the point, you can tell these people would never be able to comprehend software engineering... they have no idea that for every invisible car in front of every dumbass driver like them, there is a real car way back that has to sit through two lights. (side effects of bugs and inefficient hash tables) Worse, these dumbasses do this in the left lane so it keeps a host of others from being able to get past their big fat ass into the turn lane.

Simple queueing theory escapes these people.

Computers will someday take their jobs.

Sometimes it motivates me to code faster... "There goes your job beotch! Get used to mac and cheese..."

But once in a while I am in a position to be able to be stopped at a light, and note that next to me is one of those "gapsters" and then pull my car (or motorcycle some days) into that invisible car's spot. The gapster gets so mad sometimes... >:-> so much satisfaction I almost feel guilty...

Queueing theory rules... LOL

Side Effects are the Root of all Evil
- LISP

One week worth of pills for me as a Bipolar-I + Autism + ADHD patient. I have to take them all just to stay sane, productive and anxiety-free, at least partially. Here’s what’s here:
- Hydroxysine — a non-benzo (read not addictive) anti-anxiety pill
- Quetiapine + Lamotrigine — the number one anti-bipolar combo
- Atomoxetine — a non-amphetamine anti-ADHD pill
- Fluvoxamine — an antidepressant with anti-anxiety side effects

What is the best time of day to take caffeine with the least side effects and the most "therapeutic" effects?

And from which source? Coffee, guarana, kola nuts?

I think I understand now why people dislike continuation passing style for side effects. The continuations passed to the action can be called in any pattern, there's no inherent guarantee that an error handler cannot be called just because the corresponding success handler had already been called. In this regard they act like jump points in assembly more than functions in an equation.

I don't think this is such a massive problem. The entire imperative world is built on such things. I definitely think though that this model does not mix with autocurry.

Recently had an issue where we forgot to deploy some API updates on live when we pushed an app version live (we test on dev/staging)

Does anyone have any experience in mitigating this risk? Can't do a final test on live since that has permanent side-effects (e.g. Automated emails getting sent to other users)

hi

November 28/29 2018

I was in a different world. I experienced this different world. It is beautiful in the beginning and hell after. It is everything u need compared to our engineering world but dangerous with potential. This world kept killing me for 3 months. It was hell.

February 23/24 2019

I was in another world. Same as the first one but this one was better. I experienced everything u would ever need to experience in order to find the vision and purpose to go forward especially in sofrware engineering world. Motivation and the REASONN to go. Climb. Because of over 3 month suffering the pain was suppressed in the secondary world dimension.

March 31 2019

I am back into our world. With slight side effects from the previous two. I am left in scars from war. To travel to the other worlds is to invest extraordinary amount of time energy and effort. U have to vibrate at a different specific frequencies in this universe. It fixed me to continue but broke my focus.

I am here to tell you that u should travel to these worlds with extreme caution. You will know when to do it. You will know what i am talking about. When you do it, pull back quickly and continue in the software engineering regime. This message is abstract and cryptic. You will understand it when that day in your journey comes. Everyone will understand.

Never have the focus broken.

Heroku.
I don't like setting up servers and things. I know how to (I spent 1.5 years using archlinux and I know a lot on what's going under the hood). I like the functional paradigm where the same input yields the same result. I don't like having side effects although I know they can be necessary.
I would have to create a script to handle the configuration process instead of spending hours redoing it.
That's what I love about Heroku even if it's pricey. Almost no configuration at all. Attach some addons, configure a few env variables and everything else is in the code.

I finally used jQuery in Angular 5 to animate numbers. I am also using angular animations Hostlistner too many things to manipulate Dom. I am wondering about side effects. For now everything is cool?!!!!!!

val true : bool = isFrustrated(me : Human)

1) Honestly fuck SML. Who's goddamn idea was it to make a useless fucking programming language that does absolutely nothing relevant unless you're trying to learn recursion. Who's fucking idea was it to not be able to even have side effects. And who gives a shit if you can explicitly declare the type of variables on every single fucking line that's what comments are for if you really need it. All this is aside from the fact that nobody ever has been like "OH UNMUTABLE TYPES? WOW IM SO HAPPY THIS IS SO USEFUL". At this point I feel like SML is basically a DFA - ABSOLUTELY FUCKING USELESS

2) Aside from that, who's idea was it to duplicate two classes. There's 15-122 (Principles of Imperative Computation) and 15-150 (Principles of Functional Programming). So far the ONLY fucking thing different is we learned about work and span in 15-150 - OTHER THAN THAT ITS LIKE TAKING THE EXACT SAME COURSE. BUT AGAIN. So then I have to fucking sit in lecture and pay attention for that tiny bit of information that is new amongst the giant cesspool of information that isn't. BECAUSE I ALREADY LEARNED IT.
Oh and did I mention that both classes are required to graduate as a CS major? Fuck me.

Thanks devRant for helping <3

Edit: We are 4 weeks into the semester so you'd expect we'd have gotten into the new stuff by now right????

CBD oil has been used for years by individuals, who want to reduce their dependence on drugs. It was only recently that CBD was studied for possible pain relief by medical professionals. It is a highly important part of any healthy diet, because it is an important natural compound in plants.

Since the ancient Chinese first use marijuana as a medicinal treatment in 3000 BC, various cultures have used its healing properties, for a variety of medical conditions. However, in modern society, people often rely on pharmaceutical drugs to deal with their pain. One of the common problems with painkillers is that they can cause a number of side effects that can worsen your health. These side effects include depression, anxiety, insomnia, irritability, suicidal thoughts and more. Therefore, people have been turning towards natural remedies for their pain relief.

CBD oil has been shown to be very effective at reducing your pain, especially if you are taking narcotic painkillers. It is believed to stop or prevent the onset of physical discomfort, which means it does not provide temporary relief. As long as you are using it regularly, it can effectively help you overcome your pain.

In recent studies, medical professionals have suggested that the effectiveness of CBD was increased when it was combined with other herbs, such as ginger and eucalyptus. The main reason for this is that these two herbs have a great deal of medicinal qualities. Many people choose to combine these two natural ingredients to help reduce the amount of chemicals in their body, which will lead to a reduction in pain. By taking these products together, you will feel a reduction in pain faster than ever before.

You need to take care when using these products, however, as it is important to make sure that you do not take more than one product at a time. Taking too much of a product can actually create a higher chance of adverse reactions.

People have discovered that by taking CBD oil, they can relieve their pain, without relying on pharmaceutical drugs. If you have been using painkillers for a long period of time, try using a supplement to help you get the relief you are looking for.

Another great thing about CBD oil for pain relief is that it will help you maintain a healthy appetite. Studies have shown that when people eat foods high in CBD, such as hemp seeds and hemp oil, their bodies release natural hormones to help them fight off hunger.

If you are interested in finding out more about CBD oil for pain relief, check out. They can tell you about the various uses of the oil, the different strains of it and what to expect from it when using it.

we have been working... we swear...

this is right at the end of a project which was artificially extended because the review process wasn't setup in time. we've had to do certain things the product owners way, whilst shaking our heads and this useful chart is one of the side effects. sidenote, product owner is looking at this chart and showing it to higher ups, trying to show progress being made... i give up.

As a junior, mild and hacky OOPer/TDDer I once worked with an architect who professionally introduced me to functional programming obsession and TDD fanatism.

I'm not a junior anymore, I have less dev friends too, but now none of them has unforeseen side effects or unexpected behaviour.

currently I'm feeling like a overheated gatling gun....

We'll finish at the weekend a year plus of work.

Should I be happy? Maybe.

But currently it's just frustration cause the whole week was satanic prep work.

Lots of fsicking boring shit, planning, migraine, connecting the dots.

I wish you'd get a nice dose of "fuck everything" medicine at the work for weeks like that.

Remember the chewing gum dispenser from your childhood?

Like that. ID card in. Fun pills out.

(If drugs were only without side effects and addiction.... )

Is JavaScript the Tower of Babel? What will be the long term effects of the explosion of new frameworks. I liked it when you could use a backend server side language and had JavaScript as the special sauce that could do what the backend could not do. I am sure I will be sent to hell for blaspheming the hot, new js frameworks. Oh well better to burn out than fade away.

CSS and libraries doesn't mix. Something about the lack of scoping and the unintended side effects that happen from using two different libraries that add inline style via JS. I'm looking at you, position!!!!

Fellow Ansible developers. I'm talking to you.
Are you freaking high or simply your morning pills have some serious side effects?
How do you manage to introduce a number of regressions in every fucking major release? How on earth you feel comfortable in breaking API in a minor and even bug fix releases?
You need to get me right. I really like Ansible project but those things... I imaging you every other day as a bunch of hamsters trying to find an exit in a shitty labyrinth which you call the codebase.
If you will not stop to eat and smoke those things this would became a lot worse indeed.

It's so frustrating to explain rxjs pitfalls to the manager.

To avoid the diamond problems and glitches caused by combineLatest and debounceTime(0), I decided to use single stream with nested reactivity.

Then the manager asked me to use withLatestFrom instead of combineLatest.

Sure withLatestFrom makes sense to the original author, when the original author is able to remember the reactive graph and put proper dependencies to combineLasted/withLatestFrom accordingly, but anyone else who touches the component later needs to retrace the reactive graph to avoid the glitch. Sometimes it's just impossible when many dependencies are derived from combineLatest+debounceTime(0). When no one is trained to code reactively, I don't expect people to know where to put a dependency. After many trials and errors, the only way to avoid the diamond problem is to use nested reactivity where child streams are created within root stream each time root stream emits.

The mentioned manager put all sorts of side effects in observable chains. The manager keeps saying the stream is too large when their subscription functions (sometimes nested) are way worse with litered mutations everywhere. Anything in observable can be traced by go to definition but tracing side effects usually requires global searches.

Recently, he put startWith to the end of a synced stream to fix a bug where button would collapse when there is no content (initial null emission). Rather than fixing the default height, he thinks using startWith(defaultLabel) is a good idea. Of course, he doesn't know that a synced stream should only emit 1 value on new subscription and that extra emitted value will cause rxjs glich down the pipe.

I hate corporate jobs

At the end of a request I want to ensure that both 1) persisting to the DB and 2) dispatching to the message queue is successful.

If one of these side effects fails, I want both to fail: this can be done with a distributed transaction (eg. 2PC or something similar).

My question is, how much overhead/complexity/latency does this introduce into the system? And is this even needed in the first place or am I overthinking this?