Every day.

I am a PHP developer.

Yeah, "another PHP is awful" rant... no, not really.

It's just unsuitable for some ambitious projects, just like Ruby and Python are.

First of all, DO NOT EVER use Laravel for large enterprise applications. The same goes for RoR, Django, and other ActiveRecord MVCs.

They are all neat frameworks for writing a todo app, as a better-than-wordpress flexible blogging solution, even as a custom webshop.

Beyond 50k daily users, Active Record becomes hell due to it's lazy fat querying habits. At more than a million users... *depressed sigh*.

PHP is also completely unsuitable for projects beyond 5M lines of code in my opinion. At more than 25M lines... *another depressed sigh*.

You can let your devs read Clean Code and books about architecture patterns, you can teach them about SOLID & DRY, you can write thousands of tests... it doesn't matter.

PHP is scaffolding, it's made of bamboo and rope. It's not brick or concrete. You can build quickly, but it only scales up to a certain point before it breaks in multiple places.

Eventually you run into patterns where even 100% test coverage still doesn't guarantee shit, because the real-life edge cases are just too complex and numerous.

When you're working on a multi-party invoicing system with adapters for various tax codes, or an availability/planning system working across timezones, or systems which implement geographical routefinding coupled to traffic, event & weather prediction...

PHP, Python, Ruby, etc are just missing types.

Every day I run into bugs which could have been prevented if you could use ADTs in a generic way in PHP. PHP7 has pretty good typehints, and they prevent a lot of messy behavior, but they aren't composable. There is no way to tell PHP "this method accepts a Collection of Users", or "this methods returns maybe either an Apple or a Pear, and I want to force the caller to handle both Apple/Pear and null".

Well, you could do that, but it requires a lot of custom classes and trickery, and you have to rewrite the same logic if you want to typehint a "Collection of Departments" instead of "Collection of Users" -- i.e., it's not composable.

Probably the biggest issue is that languages with a (mostly) structural type system (Haskell, Rust, even C#/JVM languages to some degree, etc) are much slower to develop in for the "startup" era of a project, so you grab a weak, quick prototyping language to get started.

Then, when you reach a more grown up phase, you wish you had a better type system at your disposal...

I really hate this company.

The code is a disaster. Every single other employee is a salesperson. Nobody has any bloody clue what I do or how difficult it is. They don't care about stability (unless things are crashing), maintenance (until crashing), code quality (until it delays features), or anything apart from shiny new features they can sell. The boss (the king salesman, if ever there was one) doesn't know how to manage, but tries to by acting like his "nice asshole" self -- he's an asshole that gives you passes, makes sure it's bloody obvious that he's doing it begrudgingly, yet everything is still absolutely your fault. If he arbitrarily decides it's too much your fault, he stops being "nice" and flips out on you in front of everyone. That's a "nice asshole": an asshole who can barely even pretend to be nice.

Fuck him.

And you know what? I really hate having to work next to these fucking birds, too.

Today was our weekly conference call, and I was both late and unprepared. I was too focused on my work, and got a ping 4 minutes into the meeting, so I obv didn't have time to prepare. Boss was also pissy today, and I didn't have much to show for my week, thanks to lots of little "OMG NEED ASAP" shit projects that all took too long, pushing back what I was actually supposed to work on. Which didn't get finished, of course, and today that project was "the most important" -- I suspect simply because it wasn't finished. AGADJFSKL. Cue the birds fucking screaming and never fucking shutting up no matter what I did. Blanket? No effect. Spray bottle? SCREAM MORE! Boss was yelling at me, the birds were screaming, and I couldn't think. Goddamn fucking disaster.

and yes, we have a macaw. A macaw and over 20 cockatiels. Said macaw decided today was a lovely day to just fucking SCREAM non-stop, and the tiels were doing their best to keep up. Thinking clearly during this cacophony? Not gonna happen.

Wait, "go elsewhere," you say? Somewhere quieter? Where is this "elsewhere?" We live in a fucking tiny house, and during the call it was (and still is) filled with sleeping people, and surrounded by a fucking desert. Who the fuck thought living in the desert was a good idea, anyway? Like, seriously. What brainless moron thought "You know what? This is a great place! Let's settle down right here," while trudging through the scorching sand and dust, looking at the basically lifeless horizon filled with large, hot, dry, dusty, barren rocks (aka "mountains"), and fucking dying from thirst? Probably someone so delirious from heatstroke they never actually recovered, and continued raving that it's a goddamn paradise to their heat-addled imbecile followers. I really hope they hallucinated a la-z-boy in place of a hedge of teddybear cholla and died an excruciating and prickly death. Fuck that guy/girl, too.

But I digress.

I seriously need an office that isn't a 30 min drive into gang-central. I'd work outside, but I live in the middle of the bloody fucking desert, and get heat exhaustion within about half an hour. Everywhere else in the house people bother me almost incessantly.

just. FUCKING FJASKLDFJGAG.
I HATE THIS PLACE SO SO SO MUCH.

'I've had such Zen lately,' Alex said. Maybe then, but lately? I've just been too exhausted and burned out from putting up with all this shit to get angry. Days like today? I could pour kerosene over everything and laugh as it all just burned to ash.

I fucking hate Internet of Things, I think that it's a ridiculous idea to connect things, that work perfectly fine, to the internet.
The 'convenience' you get is minimalistic and most of the time non existent.
It is also often insanely insecure and expensive. The burdans it brings with it most of the time just outweigh the positive sides of it.

Now today happened something that made me hate it even more. Today was the First Lego Lego (Lego competition with ev3 robots, etc.) and one part of the tournament is to find a solution for a given problem. This year the general topic was hydro-dynamics and so the problem was how you can reduce water usage and 'save' water.

Our idea was to make reusable coffee cups and give them to the local coffee shops. One time use paper cups use take around 400ml water when produced) Basically you buy a cup once for 5 bucks and you get your coffee served in it. After drinking the coffee you return the cup to a local cafe and get a chip as pawn. When you buy your next coffee, you give them your chip and get it served in another reusable cup. The are at the moment already around 1000 cups going around the city.

Now this was our idea and we got ranked third. I am not too mad about our rank but what really drives me fucking mad is the team who ranked first.

Their idea was to make a pump (using an arduino) and a humidity sensor which you stick into a plant and the pump pumps water when the plant is too dry.
However (you probably guessed it already) they went a step further and connected it to the internet. They also made a web 'interface' for it so you can control the pump with your smartphone / computer / smartwatch / tv / whatever the fuck is connected to the internet nowadays 'thanks' to the iot 'revolution'.

So it is a pump that waters your plant when it is too dry BUT it is also connected to the internet.

WHY THE FUCK DOES THIS HAVE TO BE CONNECTED TO THE INTERNET.

"Oh look it is connected to the internet, wow awesome, oh it is also 'smart'. oh cooool. Nice I don't have to water my plants anymore"

A funny thing is that one of my friends built basically the same thing without connecting it to the internet. He built a small box with a pump and a humidity sensor that measures if the dirt is too dry and then waters the plant. It checks every few hours and the also is a small 16x2 LCD and a knob that you can turn to control how much water it should give the plant each time it waters it. He built it and I programmed it for him. Works perfectly fine and I don't see any reason why there should be any need to connect something like this to the internet.

Anyway we got ranked third, they first. I guess we should connect our coffee cups to the internet in some way ...

So my localization algorithm actually runs onboard my YouBot :)
My paper was basically torn apart by my professor, so I had to write some new classes and redo the whole experimental section. And all the other sections too. I resubmitted it to him after revisions, and the second iteration was way better - I'm really close to final paper level :)
I told my professor and postdoc that I will appreciate more support and positive feedback, because so far our communication was only very dry criticism. For me it's really devastating, because feeling like I constantly disappoint people just kills me on the inside.
It seems like they took it to heart, they have been nicer to me in the last few days :)

I absolutely hate the way we are taught programming in Indian colleges.

FML #1: I'm pursuing a UG CS course, and this semester, I only had one subject of Computers, that too only 1 credit. The rest with all electronics.

FML #2: In that 1 credit course, we had to make a C++ project which had "data handling". No one cares if you build something cool or not, just that a project should have "extensive use" of data handling.

FML #3: Source code had to be >= 1000 lines. This is the only place where ADDING MORE LINES OF CODES THAN REDUCING IT is appreciated. Had to stuff my code with all kinds of comments and violating the basic principle of DRY.

So, yeah, we're fucked big time. 😥

I'm such an idiot.

Spilled water on my MacBook today. Not that much water, but the cup landed right in the middle of my keyboard.

Worst part is I was gaming with my sister and didn't want to stop. So I wiped it off and shook it out a bit and kept playing. A bit later the screen started flickering and eventually went black.

Finally my brain turned on and I switched it off, shook out some more water, and set it up to dry. Just hoping it's not too late.

At least the drying setup recommended by the internet is pretty hilarious looking.

Now we play the waiting game. They say 72 hours before turning it on again. Seems a bit extreme. Will there still be moisture evaporating 3 days later? Not sure I can wait that long to see if it's toast.

Such an idiot.

A few hours ago I decided it was a good idea to to clean up my keyboard. I did so and took a walk leaving the keys to dry.

After I came back I hoovered the -board and decided to put back the keys. I started with the special keys since they were the easiest to find (and some required a metal thing).

Now, I was quickly made aware of something that I had never known nor noticed before. Bear with me here as I'm not a person that cares too much about hardware unless I need to. (Hardware here meaning stuff like mice, keyboards, headsets, and stuff like that). But I learned that

Not all keys are the same size. They look really similar to someone like me. But I manned up and put the keys back.

A little under 1.5 hours later and I now posses a keyboard that is in uncanny valley. It doesn't feel like it though, and it shouldn't be that big of a problem since I never look at my keyboard anyway.

Messaged one of my m8's about and this was his reply

"nope
one kind per row
usually says the row on the underside"

Now fantasize about the elasmobranch fish which is characterized by a cartilaginous skeleton of which I am the proprietor at what he said. I pulled a key out and, sure enough, "C28 R1".

Now I am not sure about the 28th column, but it did fit in the first row.

Fuck me

!dev

I‘m not shitting you, a can of Guinness just fucking exploded in my bed room..

Last weekend i had a few drinks too much and I took a Guinness to my room to „watch a movie and fall asleep“. I fell asleep before even starting a movie. So I didn’t even open the can.

Today I was looking for a cable on my night table and accidentally hit the can with my elbow.
It just fell in the side and FUCKING EXPLODED. The can is split in half.
My whole bed, my good shoes, my mattress, the floor, my bills and EVERYTHING IN A RANGE OF 5 FUCKING METERS IS SOAKED.

How the fuck can that even happen?

Tried to clean everything with water and opened the windows to get my my shit dry again, but now I have to sleep on the couch in the living room until that stuff is try again..😤😤😤

Need a Guinness to calm down.

I know cans can „leak“ if it’s too hot but we had 19C max in the last week..

Happy weekend to you..

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

For the last time, SLOC is not a measure of anything.
Have too many, the code probably isn't DRY.
Have too few, you probably don't follow a style guide and have 120 char lines because you invented "oneliners" which you were so proud of that you had to put it in there.
Have just the right amount, and the code likely suffers from both of these at the same time.

My partner says I'm too much of dry logic and lacking in emotions. The way I want to find logic in everything and ignore illogical spontaneous emotions... Isn't helping me in here.
Just wanted to vent out and ask whether this is the curse of the nature of work... with tech I am in (I fantasise it to be that) or is it just My individual problem?

Damn this week topic is hard.

I am gonna go with managing a team. I have to use the DRY SOLID YAGNI KISS on daily basis at non-dev tasks too.

The railway service in Sydney is called CityRail.

Fuck CityRail!

It's so unreliable that service disruption is to be expected when the weather is too hot, too cold, too wet, or too dry. If it rains, some services will be cancelled while the rest face delays.

Fuck CityRail!

The rail network is so dilapidated it costs the government millions of dollars each year for maintenance, despite charging a fare that is one of the most expensive.

Fuck CityRail!

Now I'm typing this because I've be stuck on this train for the last hour and there little hope for me to reach home before fucking MIDNIGHT!

FUCK CITYRAIL!

They initially offered replacement service but later retracted.

Fuck CityRail!

This stupid computer is in clamshell mode connected to my screen and mech %99.999999 of the time. I take it with me on a trip and the down arrow key breaks off (little plastic shit-thing snapped off)..WTF? 2013 Macbook that has about 5 hours of total keyboard-use, at best.

Walk into the Apple shop in Varna, 3 Euros and I'm back in action.

ahhhh fuck..it was probably my fault clacking too hard.

Good sushi here and my dry February has happily turned into large pints of Kamenitza...

Cheers from Bulgaria, you fucks..

The year was 2006. During the first half of my career, I use to work in the NOC. This was before I made my transition to software engineer. I worked on the third shift for a bank services company. The company was on a down turn. Just years earlier they just went public, and secured a deal with a huge well known bank. Eventually they entered a really bad contract with the bank and was put into a deal they couldn't deliver on. The partnership collapse and their stock plummeted. The CEO was dismissed, and a new CEO came in who wanted to "clean things up".

Anyway I entered the company about a year after this whole thing went down. The NOC was a good stepping stone for my career. They let me work as many hours as I liked. And I took advantage of it, clocking in 80 hours a week on average. They gave me the nick name "Iron Man".

Things started to turn around for the company when we were able to secure a support contract with a huge bank in the Alabama area. As the NOC we were told to handle the migration and facilitate the onboarding.

The onboarding was a mess with terrible instructions that didn't work. A bunch of software packages that crashed. And the network engineers were tips off, as they tunnel between our network and the banks was too narrow, creating an unstable connection between us and them. Oh, and there were all sorts of database corruption issues.

There was also another bank that was using an old version of our software. The sells team had been trying to get them off our old software for over a year. They refuse to move. This bank was the last one using this version, and our organization wanted to completely cut support.

One of the issue we would have is that they had an overnight batch job that had an ETA to be done by 7 AM. The job would often get stuck because this version of the software didn't know how to fail when it was caught in an undesired state. So the job hung, and since the job didn't have logging, no one could tell if it failed unless the logs stopped moving for an hour. It was a heavily manually process that was annoying to deal with. So we would kill the JVM to "speed" the job up. One day I killed the JVM but the job was still late. They told me that they appreciated the effort, but that my job was only to report the problem and not fix it.

This got me caught up in a major scandal. Basically they wanted the job to always have issues everyday. Since this was critical for them, all we needed to do was keep reporting it, and then eventually this would cause the client to have to upgrade to our new software. It was our sales team trying to play dirty. It immediately made me a menace in the company.

For the next 6 months I was constantly harassed and bullied by management. My work was nitpicked. They asked me to come into work nearly everyday, and there was a point I worked 7 days with no off days. They were trying to run me so dry that I would quit. But I never did.

On my last day at the company, I was on a critical call with a customer, and my supervisor was also on the line. My supervisor made a request that made no sense, and was impossible. I told her it wasn't possible. She then scalded me on the call in front of customers. She said "I'm your supervisor, you're just a NOC technician, you do what I say and don't talk back". It was embarrassing to be reprimanded on a call with customers. I never quite recovered from that. I could fill myself steaming with anger. It was one of the first times in my adult life that I felt I really wanted to be violent towards someone. It was such a negative feeling I quit that day at the end of my shift with no job lined up.

I walked away from the job feeling very uncertain about my future, but VERY relieved. I paid the price, basically unable to find a job until a year and a half later. And even was forced to move back in with my mother. After I left, the company still gave my a severance. Probably because of the supervisor's unprofessional conduct in front of customers, and the company probably needed to save face. The 2008 crash kept me out of work until 2009. It did give me time to work on myself, and I swore to never let a job stress me out to that degree. That job was also my last NOC job and the last job where did shift work. My next few jobs was Application Support and I eventually moved into development full time, which is what I always wanted to do.

Anyway sorry if it's a bit long, but that's my burnout story.

Am I the only one that cringes when I see software developer consistently ranked as one of the best jobs to have? Are other jobs that horrible that this is as good as it gets? I’m probably too cynical I suppose.

I feel like I was seduced by the fun of programming only to have the corporate enterprise suck my soul dry.

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

Debugging a task, that's sending emails to too many customers.
Supervisor: "Never mind, just test in production, there is a dry run flag for the tasks."
Just in case I test locally...
Flags tried:
--dryrun="TRUE" => Error, failed to send mail.
--dryrun=TRUE => Error, failed to send mail.
--dryrun="true" => Not trying to send mail.

If it's THIS PICKY a little more documentation would be nice.
And by a little more I mean: more than the task base class in a giant php monstrosity without phpdocs expecting its code to be self-documenting.

!dev

Hello fellow ranters.
I'm looking for some inspiration in the kitchen.

Lately I've been on somewhat of a health binge. So I'm looking for some ways to make my dry and uninteresting food more interesting. Like a sauce or something.

I usually like hummus a lot. But it's getting old. Does anyone have any fun I can take inspiration from?

I'm not looking for recepies, just inspiration.

Don't know if I need to say this but obviously I'm not looking for unhealthy stuff. So nothing too fat.

!dev

It never seize to amaze me how so many seem to think more base = better sound, even to the point where the sound is so muddy and unintelligible that it sounds like you’re listening to the upstairs neighbor having a party on a Saturday night.

Even if you only listen to electronic music with heavy bass, there is usually some treble or mid tones that just gets obliterated with too much base. The only situation I feel like it could make sense was if you primarily listen to jet engine noises or whales mating on dry land.

Come on, treat your ears and honor your artists by using some quality headphones that can sound like it’s meant to sound.

You know, I don't mind getting dragged if I deserve it. But it would be nice to have ALL the information I need to make an estimate BEFORE you hang me out to dry.

First I was told that work on this issue could be kicked down the road since we were getting big contracts. The next day the issue was in the sprint.
I tell you I won't be able to get it done with the business critical stuff you said absolutely had to be done that sprint (turns out we had 3 months of leeway even before COVID). You say alright cool. We push it to next sprint. The next day you say we have been pushing that issue too much and we absolutely have to get it done this sprint. At least have it so QA can look at it by Tuesday.
I give a preliminary look to QA cuz I found a bug, but they can test other shit about this fucking issue, but then get shut down fucking again because it isn't code complete.
STOP. MOVING. FUCKING. GOAL POSTS. AND. GASLIGHTING. ME.

And as a bonus, I disagree with the necessity of this work in general. I think it's fucking stupid, unnecessary, and zero value added. It's a management jerkoff issue that is going to piss off all of our users.

Hey guys , how are you dealing with covid19 health-wise you know, mentally and physically? I know most of people aren't affected (and i hope you remain the same) or won't care much, but me and my family has always been too anxious.

We had been taking a lot of precautions, but recently my father got sick followed by myself and then my mom.

Those are some mild sickness( <100°F fever, weakness little dry cough) and it maybe purely a coincident that we all got same symptoms and felt sick one by one , but we would be foolish to not consider coronavirus a cause.

And with that realisation comes another wave of panic down my sick parents mind who immediately go into state of paranoia.

How are you people dealing with this? Do you think your strategies and preparations against the virus are enough? Also how exactly are you applying safety measures in home, if someone is sick? Different soaps, different rooms etc?
Stay safe guys . Let's chat to feel better

When you are reviewing a PR in which the author has used utilities/libraries that were written by you(which were very generalized and DRY but required for you to read the docs to clearly understand their usage). But instead of using it properly they modify it for their specific usage and made a freaking PR. 

I just can't wait to finish the review and slap their face with a printed copy of the FUCKING docs. 

Seriously, read the goddamn docs. And, if you do change the lib, please update the doc too.

Compromise.

I think that sums up development pretty much.

Take for example coding patterns: Most of them *could* be applied on a global scale (all products)… But that doesn't mean you *should* apply them. :-)

Find a matching **compromise** that makes specific sense for the product you develop.

Small example: SOLID / DRY are good practices. But breaking these principles by for example introducing redundant code could be a very wise design decision - an example would be if you know full ahead that the redundancy is needed for further changes ahead. Going full DRY only to add the redundancy later is time spent better elsewhere.

The principle of compromise applies to other things, too.

Take for example architecture design.

Instead of trying to enforce your whole vision of a product, focus on key areas that you really think must be done.

Don't waste your breath on small stuff - cause then you probably lack the strength for focusing on the important things.

Compromise - choose what is *truly* important and make sure that gets integrated vs trying to "get your will done".

Small example: It doesn't really matter if a function is called myDingDong or myDingDongWithBells - one is longer, other shorter. Refactoring tools make renaming a function an easy task. What matters is what this function does and that it does this efficiently and precise. Instead of discussing the *name* of the function, focus on what the function *does*.

If you've read so far and think this example is dumb: Nope... I've seen PR reports where people struggled for hours with lil shit while the elephant in the room like an N+1 problem / database query or other fundamental things completely drowned in the small shit discussion noise.

We had code design, we had architecture... Same goes for people, debugging, and everything else.

Just because you don't like what weird person A does, doesn't mean it's shit.

Compromise. You don't have to like them. Just tolerate them. Listen. Then try to process their feedback unbiased. Simple as that. Don't make discussions personal - and don't isolate yourself by just working with specific persons. Cause living in such a bubble means you miss out a lot of knowledge and insight… or in short: You suck because of your own choices. :-)

Debugging... Again compromise: instead of wasting hours on debugging a problem, ASK for help. A simple: Has anyone done debugging this before or has some input for how to debug this problem efficiently?... Can sometimes work wonders. Don't start debugging without looking into alternative solutions like telemetry, metrics, known problems etc.
It could be a viable, better long term solution to add metrics to a product than to debug for hours ... Compromise. Find a fitting approach to analyze a problem instead of just starting a brute force approach.

....

Et cetera et cetera.

CircleCI takes the cake for the most annoying of constant development advertisement campaigns on YouTube, change my mind.
I mean, the product is nice and everything, but what the hell? Why should *I* make sense of your changelog - just go and show what it does in practice! Ugh, why I must teach you marketing, CircleCI, smh...

That rabbit in my grandpa's left table drawer, in the home I grew at. I wanted to finally catch it, and kill it. I was bad with animals all along, especially this one. My grandpa died the year before I was born, and my grandma said we would've got along really well. So much to talk about, a scientist to an engineer. So, I travelled back, but my home somehow turned from a city stone-walled house into a half-soaked, decaying wooden one. I caught that rabbit though, but while I was holding it at its neck and twisting it, it somehow disappeared, distributed evenly as if I were twisting a crayon. I was trying to find it, but in that left drawer, among century-old pencils and that red liquid thermometer I played with as a kid, only a faded out, dusty duckling resided. I picked it up, and unlike the rabbit, it was paper, no, cigarette paper thin. It wasn't hostile. It wasn't trying to run away. It just turned from yellow to grey, feathers leaving my fingers covered in fine dust. I realized it will never die, dwelling and decaying there forever, happy.

I did my calculations, and I knew for a fact when and where the rabbit should've appeared. It was the middle drawer, not the left one. I opened it and looked in anticipation how something chewed through the bottom. I caught it, but it was no rabbit, it was an alive, rubber rat. The rubber was white turned grey, old, aged, dusty, probably Soviet. I poked the rat's eye with a pen rod, but the rat's body inflated a bit, leaving it invincible. It was mocking me.

Of the same white rubber, a ball appeared. I knew for a fact it was alive too, I felt the bones inside holding it. I found its lips, and was prying it open. The massive, dry mouth emerged, with a full set of human teeth, albeit wider and nastier ones. Huge eyes looked at me. It was alive, it was intelligent. It was my grandpa's personal financial assistant all along. It told me to leave the rat and the rabbit alone. He told me not to worry about the ducking, as it was in safe hands.

It made friends with my brother during the "blue age", when he was wearing thin, worn out rugs instead of clothes, tiny faded blue flowers on them, screaming and annoying my grandma he lived with in that room, not a single person other than the two in sight. The house was slowly submerging. The water was rising.

I think my worst habit is that I create too much DRY code. Sometimes code gets repeated when I'm just too focused on getting a feature to work and makes it hard to refactor later :/

I'm so fed up with Codecademy. I payed for the pro, and I admit I haven't been able to consistently use it everyday as I would like. But every fucking time I would be on a lecture of some sort, I swear to fucking to christ it's the most buggy, uninformative piece of shit! And everytime you're in deep into subjects, the information is beyond unclear!

AND GOD FORBID YOU NEED A FUCKING HINT! they leave you to dry saying in the hint that "Look back at the previous sections" or "try to remember the steps you've learned"

No you stupid fucking bitch for a site. I clicked on the hint because I needed an answer as to what I'm doing wrong, and to something that can stir me in the right path. My god....I feel so stupid for giving PRO a chance. I thought maybe it would be nice to have some sort of professional site would be useful.

I swear this early afternoon I was spending fucking forever on the first few lectures of HTML trying to figure out what the actual fuck is wrong with the system fucking up not letting me change directories. And the community was no help whatsoever to the issues at hand.

Again, why the fuck is Codecademy so goddamn buggy!? Sure it may be a fun site to fuck around with to get your feet wet on the free version. But is it too much to ask for some good actual lessons that are being payed for!?

Idk anymore. I'm sticking to just YouTube and other free help. This is the last time I spend a fucking penny to any site that's supposed to teach something valuable.

I feel so upset because I feel like I wasted my money and time on something that I thought could've helped a lot.

If anyone was asking if PRO is worth it....definitely not! Please don't waste money with it! Don't make my mistakes, stick to YouTube and other free sources! The least I can do is warn people about spending money on this site. Trust me it's not worth it. It may not seem bad in the beginning, but once you go deeper it becomes clear the issues.

If anything stick to only free!!

hey uh, this is a rant about phantom forces, if you don't know what it is, look it up, anyways, that's really it.

so, i've been playing this game very actively called phantom forces and its a good game but its been ruined and the fun has pretty much been taken away. the community is dead and terrible, the developers don't care and the game is just falling off.

what i consider community is the youtube scene, and now as of january 1st, 2022, there's nothing left that's actually interesting besides godstatus and moons fps studio. honestly, its so dry and i'm sick of it.

i'm tired of seeing shitty best setup videos and gun reviews. i hate somesteven and strider and then, there's nothing to actually watch so i just watch brain-numbing shitty videos about stuff.

and then theres the developers, stylis studios is a great development team, i'll give you that but the sheer ignorance of their team is so fucking much.

its kinda obvious they don't really care about adding new features or anything new that isn't guns and its fucking sickening. just to see the same old updates, every fucking month man, its annoying and tiring.

i'm fucking tired of just seeing ape shit guns that are too high for regular players to actually unlock. like i know they're trying to please the growing number of 200+ rank users but its terrible, they haven't done a gun below rank 200 or 100 in forever. the last time they did it was like 6 months ago or something.

we've been asking for shit for years and they haven't given it to us and its fucking tiring. asking for daily quests, new features, more grips, vehicles and shit like that is obviously never gonna happen and thats the fucking problem. they don't care about their community.

but anyways, thats really all i want to say, might make a follow up post later. if you want to add your 2 cents down in the comments, you can do that. bye