After listening to two of our senior devs play ping pong with a new member of our team for TWO DAYS!
DevA: "Try this.."
Junior: "Didn't work"
DevB: "Try that .."
Junior: "Still not working"

I ask..
Me:"What is the problem?"
Few ums...uhs..awkward seconds of silence

Junior: "App is really slow. Takes several seconds to launch and searching either crashes or takes a really long time."
DevA: "We've isolated the issue with Entity Framework. That application was written back when we used VS2010. Since that application isn't used very often, no one has had to update it since."
DevB: "Weird part is the app takes up over 3 gigs of ram. Its obviously a caching issue. We might have to open up a ticket with Microsoft."
Me: "Or remove EF and use ADO."
DevB: "That would be way too much work. The app is supposed to be fully deprecated and replaced this year."
Me: "Three of you for the past two days seems like a lot of work. If EF is the problem, you remove EF."
DevA: "The solution is way too complicated for that. There are 5 projects and 3 of those have circular dependencies. Its a mess."
DevB: "No fracking kidding...if it were written correctly the first time. There aren't even any fracking tests."
Me:"Pretty sure there are only two tables involved, maybe 3 stored procedures. A simple CRUD app like this should be fairly straight forward."
DevB: "Can't re-write the application, company won't allow it. A redesign of this magnitute could take months. If we can't fix the LINQ query, we'll going to have the DBAs change the structures to make the application faster. I don't see any other way."

Holy frack...he didn't just say that.

Over my lunch hour, I strip down the WPF application to the basics (too much to write about, but the included projects only had one or two files), and created an integration test for refactoring the data access to use ADO. After all the tests and EF removed, the app starts up instantly and searches are also instant. Didn't click through all the UI, but the basics worked.

Sat with Junior, pointed out my changes (the 'why' behind the 'what') ...and he how he could write unit tests around the ViewModel behavior in the UI (and making any changes to the data access as needed).

Today's standup:
Junior: "Employee app is fixed. Had some help removing Entity Framework and how it starts up fast and and searches are instant. Going to write unit tests today to verify the UI behaivor. I'll be able to deploy the application tomorrow."
DevA: "What?! No way! You did all that yesterday?"
Me: "I removed the Entity Framework over my lunch hour. Like I said, its basic CRUD and mostly in stored procedures. All the data points are covered by integration tests, but didn't have time for the unit tests. It's likely I broke some UI behavior, but the unit tests should catch those."
DevB: "I was going to do that today. I knew taking out Entity Framework wouldn't be a big deal."

Holy fracking frack. You fracking lying SOB. Deeeep breath...ahhh...thanks devRant. Flame thrower event diverted.

Circular linked list

Aaaah...I just got back from a meeting because of a production data problem caused by an analyst who keeps making mistakes that screw up client data. I wrote a program to automate most of it and everybody initially accused me of having a buggy program, only to find out she wasn't using it, never did.

"Why aren't you using the program then?" was asked. "Oh, well, I just understand my way better," she replies, "When I make a mistake at least I understand why."

Pause....

"Then, um, if you know you're making a mistake, why don't you fix it?"
"Because my process is so manual and labor intensive sometimes it's not worth it to go back and fix it, because I'd have to do everything over again, and you guys are much better at fixing this stuff than I am."

I indicated that everyone is too busy to stop and fix her mistakes, to which she then asks:

"So if you can't fix my mistakes, what am I supposed to do?"

Manager: Hey how come you left so many comments on my PR?

Dev: Well you’ve just recently learned how to code so there’s going to be a lot of things to learn beyond what you’ve picked up in your online coding tutorials. Don’t worry it’s only minor things like you put everything all in one function, left outdated comments in the code, have if statements 4 levels deep, have a console.log after every line of code some of which log .env variables, skipped error handling, cast to “any” a bunch instead of using more specific types, didn’t write any tests and some unrelated tests are now failing due to a circular dependancy.

Manager: THAT IS SO DISRESPECTFUL!!APPROVE MY PR IMMEDIATELY. IT WASN’T EVEN EASY FOR ME TO CREATE THE PR, NOW I HAVE TO MAKE AN UPDATE!? YOU’RE THE DEV, YOU SHOULD FIX IT NOT ME!! NEVER COMMENT ON ANY OF MY PRS AGAIN.

A dictionary is just a whole bunch of circular references.

Handed in my project today on one of those circular disks with a hole in it 🤔.

It felt so nostalgic, haven't touched such a thing in many many years. The sound of the disk turning inside the computer when we run it as a test was pretty great.

Dev: Hi Guys, we've noticed on crashlytics that one of your screens has a small crash. Can you look?

Me: Ok we had a look, and it looks to us to be a memory leak issue on most of the other screens. Homepage, Search, Product page etc. all seem to have sizeable memory leaks. We have a few crashes on our screens saying iPhone 11's (which have 4gb of ram) are crashing with only 1% of ram left.

What we think is happening is that we have weak references to avoid circular dependencies. Our weak references are most likely the only things the system would be able to free up, resulting in our UI not being able to contact the controller, breaking everything. Because of the custom libraries you built that we have to use, we can't really catch this.

Theres not really a lot we can do. We are following apples recommendations to avoid circular dependencies and memory leaks. The instruments say our screens are behaving fine. I think you guys will have to fix the leaks. Sorry.

Dev 1: hhhmm, what if you create a circular dependency? Then the UI won't loose any of the data.

Dev 2: Have you tried looking at our analytics to understand how the user is getting to your screens?

=================================

I've been sitting here for 15 minutes trying to figure out how to respond before they come online. I am fucking horrified by those responses to "every one of your screens have memory leaks"

circular dependency when you realize you have a

Well, today I spent the whole day hunting a circular dependency that I introduced and was breaking the whole application.

Fuck me.

So we have an API that my team is supposed send messages to in a fire and forget kind of style.

We are dependent on it. If it fails there is some annoying manual labor involved to clean that mess up. (If it even can be cleaned up, as sometimes it is also time-sensitive.)

Yet once in a while, that endpoint just crashes by letting the request vanish. No response, no error, nothing, it is just gone.

Digging through the log files of that API nothing pops up. Yet then I realize the size of the log files. About ~30GB on good old plain text log files.

It turns out that that API has taken the LOG EVERYTHING approach so much too heart that it logs to the point of its own death.

Is circular logging such a bleeding edge technology? It's not like there are external solutions for it like loggly or kibana. But oh, one might have to pay for them. Just dump it to the disk :/

This is again a combination of developers thinking "I don't need to care about space! It's cheap!" and managers thinking "100 GB should be enough for that server cluster. Let's restrict its HDD to 100GB, save some money!"

And then, here I stand trying to keep my sanity :/

TL;DR you suck, I suck and everybody sucks, deal with it....

------------------------------------

Let me let off some steam, since I've had enough of people hating on languages "just because"

Every language has it's drawbacks and quirks, BUT they have their strengths also. Saying "I hate {language}" is just you being and ignorant prick and probably your head is so far up your ass that you look like an ass hat. With that being said, every language is either good or bad depending on the developer writing in it. Let's give you an example:

If I ware to give you a brick and ask you to put a nail in a plank, can you do it? Yes, it will be easier if you do it with a hammer, but you have a brick, so hammer is out of the question. If you hit your thumb while doing it... well... sorry, but it is not the bricks fault - it is YOU!

JavaScript, yes it has a whole lot of problems, but it works, you can do a ton of stuff and does a good job at that, it is evolving through node and typescript (and others, just a personal pref), BUT if you used js when you ware debugging that jquery (1.0) plugin written in the free time of a 13 yo, who copy pasted a bunch from SO, well, it is not js' problem - deal with it. Same goes for PHP, i've been there where you had a single `index.php` with bazillion lines of code, did a bunch of eval and it was called MVC, but it also is evolving.. thing is all languages allow you to do some dumb stuff so YOU have to be responsible to not fuck it up (which you always DO btw, we all do). Difference is PHP/JS roll with it because the assumption is that you know what you are doing, which again - newsflash - you don't.

More or less I would blame that shit on businesses which decided to go with undergrads to save money instead of investing in their product, hell, I am in a major company that does not invest that doesn't care a whole lot about dev /tech stuff and now everybody's mother is an engineer - they care about money, because investors care about money (ROI) and because clean code does not pay the bills, but money does.

If we get all of the good practices and apply them to each language every one of them has it's place, that is why there is no "The Language", even if there was, we STILL ware going to fuck it up and probably it was going to be even worse than where we are now.

Study, improve, rinse and repeat... There are SENIORS and LEADS out there that are about 25-30 and have no fucking clue about the language, because they have stuck up their heads up the ass of frameworks and refuse to take a breath of clean air and consider something different than their dogmatic framework "way" of doing things.. That is the result you are seeing. Let me give you a fresh example to illustrate where I am at atm:

Le me works with ZendFramework 2.3-2.5 (why not, which is PHP5+ running on PHP7 [fancy, eh]), and little me writes a module for said project, and tries to contain it in its own space, i.e not touching anything outside of the folder of the module so it is SELF-CONTAINED (see, practices), during 2-3-4 iterations of code review, I've had to modify 4 different modules with `if (somthing === self::SOMETHING_TYPE)` as requested by my TL, which resulted in me not covering 3 use-cases after the changes and not adding a new event (the fw is event-driven, cuz.. reasons) so I have to use a bunch of ifs in the code, to check a config value and do shit. That is the way of I am asked to do things I hate what I've done and the fact that because of CR I have lost case-coverage, a week of work and the same TL will be on my ass on monday that things are now "perfect".

The biggest things is "we care about convention and code style"... right.... That is not because of the language, not because of me, not because of the framework - it is some dude's opinion that you hate, not the language.

New stuff are better, reinventing the wheel is also good, if it wasn't you would've had a few stone circular things on your car and things ware going to be like that - we need to try and try, that is the only way we actually learn shit.

Until things change in the trade, we will be on the same boat, complaining about the same shit over and over, you and me won't be alive probably but things will not change a bit.

We live in a place where state is considered good, god objects necessary (can you believe it, I've got kudos for using the term 'God Object'... yep, let that sink in). If you really hate something, please, oh god I beg you, show me how you will do it better and I will shake your hand and buy you a beer, but until then, please keep your ass-hurt fanboy opinion to your self, no one gives a shit about what you think, we will die and the world will not notice...

Fuck the brains of circular dependency.

On a fresh install of OS X on my hackintosh.
1) Let me install HomeBrew
2) I need Command Line Tools to install HomeBrew
3) Xcode dmg is on my Android. Opens Android File Transfer tool.
4) Error: File is larger than 4GB. Need to use adb.
5) Need to install android-platform-tools, which contains adb.
6) android-platform-tools is available in brew. Goto 1).

Note: Networking is limited to tethering mobile data as Wifi chip hasn't arrived yet.

Customer: "Yeah we need <insert bonkers 12 step circular logic> to find a thing(s) in the database."

Me: "Ok let me diagram this out and I'll send it to you to review.... but man this seems like the 8th version of this we're doing right?"

Customer: "Yeah well <employee Y> says they can't do B, C without this."

Me: "Wait... can't they just <insert the most simple step in the history of time> in step A, and then later on they won't have to do all this hunting later? Like you have that data at step A right?"

Customer: "Yeah but <employee Y> doesn't want to do that."

Me: "She's your direct report ....."

Customer: "Yes...."

Me: "Ok.... I'll send you the diagram and the cost estimate...."

Whatever reason sometimes it is a bit draining coding madness compared to making things actually efficient / people's jobs easier...

Someone had a question on teams about a circular dependency warning they were getting. They found a work around that would allow it. Someone else responded with this

They don't tell you this is in uni but your skill in merge conflict and circular dependency resolution is more essential in the real world than your knowledge of data structures.

One job I picked up was for an IoT Start Up. It was quite interesting work, reporting to the technical director, who was an electronics engineer, who was designing the hardware himself, they had a couple of firmware guys already, and just needed someone to take care of the software.
So they said they needed something in Azure that they could stream their data to and provide analytics for their clients. It had to be Azure, and it had to be Azure Native, and was to be Multi-client, as they had a deal with Microsoft to showcase how well Azure works in the IoT space at an exhibition/conference in 3 months time.
So I worked flat out for 3 months, on a whole variety of technology, from C++ to get the radio packets from their IoT chip, Python to run on the hub to take the data from the C++ and stream it to the cloud, Azure IoT Hubs in every continent to receive the data and store it an a Cosmos DB, and then Power BI analytics wrapped up in an Angular front end that the clients could log into.
Got it finished 2 days before the show, and they were so pleased I got flown business class to Singapore to be on the stand and talk to customers.
The first sign of trouble was when we arrived at the show to find we just had one of those little circular tables with two stools in the middle of the floor, about two feet across and no power.
No problem, I was able to sort that, swapping laptops in and out.
Microsoft were really happy with what we had, and couldn't believe I had thrown it all together in 3 months.
We picked up a potential customer for the system, a major Asian Telecoms company.
Then when we got home, the CEO swooped in. I had never met this guy before. Imagine one of the VC guys from Silicon Valley, or the CEO from the IT Crowd. You get the picture. Could talk the hind leg of a donkey, and real street smart, but no brains. He insisted on "taking it from here" and flew alone to strike the deal with the customer. Came back with an MOU in his pocket and said to me, their guys will be in touch with you.
Then I got a call. Can you send us the source code and tell us how what servers we have to run this on?
Um, its cloud native.
No, we can't use a cloud it has to be on our servers - your CEO told us that was no problem..
He hadn't even taken the trouble to find out what it was we had built, and what he was selling.

we are learning how a disk rotates in order to preserve memory on the physical computer hardware. in order for this disk to preserve memory, it has to rotate by following laws of physics as a circular sphere with sine and cosine waves on the coordinate system. these sine and cosine waves that vibrate independently and periodically, which means that the disk rotates 10,000 orbits per second. a drill rotates 2000 orbits per second. 10,000 orbits per second is fast enough to cut your hand off in less than 1 millisecond. we are learning that this disk has to rotate so fast in order to preserve the memory which was stored by the database system with sql.

on a subject called sql databases.

Reinvent the wheel workaround: Rename the wheel.

Since you cannot reinvent it, because it already exists and it's working, just call it "rolling circular object" and get away with it.

Why in hell I should call packages "namespaces"?
A package can contain a lot of things actually. It's visual, you can create an icon for it.

Namespace? is that even a word?

Next time I rent an apartment, I'll ask if they have a FuckSpace instead of a bedroom.

"Well, it's a small studio, there is only a ShitSpace and an Open EatAndFuckSpace"

Will do.

Ok what idiot calls a spinner loader element circular-progress__graphic? WHO?!

I got 999999999999999999999999999 Problems and it's a circular requirement

There is this dude called Richard Eng which is sort of famous for 2 things:
First: he is known as *the* Smalltall evangelist of mothern times. And he constantly writes about it. Which is fine since he tries to attract new users to this beautiful and simple little language.

Second: his constant bashing of other technologies, mainly Javascript stating that it is the most harmful tech known to man.

The thing is, saying "use this because that is shit" is never going to convince a community, specifically one as potent as that of the JS community. And to make it worse...the dude links his reasoning about bad languages to articles he wrote. As in "this is shit, look at my completely biased article regarding why its shit"

Once he is confronted about it he links back to his own writings. Much like christian fanatics do
"good is real because it says so in the bible"
"but how can you trust that resource?"
"Because the bible is the word of God"
"and how do you know?"
"Because it is in the bible"

Circular arguments like that cannot be taken seriously. And what this guy does for the Smalltalk community hurts more than it helps really.

Claims like those are all around us. If we were to believe or consider them depending on who said what then we would never have the amazing cluster of tech choices that we have.

Take c++. It is absolutely powerful and gives you the ability to do pretty much anything. If we were to take Linus Torvalds's word about it being shit and only having subpar development we would miss on absolutely powerful tools.

The same came to me from Evee, writer of "PHP a fractal of bad design" or the "Node.js is cancer" article.

You are never going to please anyone with anything. I go by live and let live, and whilst I don't like some technologies I certainly don't look down on those that do.

Front end developer is still getting a ticket even though the security flaw lies in the back-end.

Today, every click of the UI has an overlay of circular progress indicator indicates that there will be a synchronous actions in an asynchronous requests.

1 click = 1 loading state

So on top of my Windows update frustrations, I just found out that Microsoft has been scamming me out of money for two years!
I bought an android tablet in 2016 which came with a free 1 year subscription to Office365. They demanded credit card info, so I made sure to pre-cancel it to avoid getting charged when the year was up.
Today I find a line on my bank statement that just says 'MICROSOFT', and I think to myself: 'What the hell is that?!?'
It takes some digging for the email adress I used and trying to navigate various MS sites until I realize that those bastards have auto-renewed the subscription twice now!
I missed it last year, but luckily since I caught the latest one within 30 days I can get a full refund.
Will contact their support tomorrow to get the rest of it back. Too tired right now to deal with their support jungle of circular links and virtual assistants...

My new favourite license

# The "You Can't Have It" License (YCHI)

**Version 1.0, October 2024**

**Copyright Me. All rights reserved.**

## 1. Definitions

**1.1 This Software**
Means the source code, object code, binaries, documentation, and anything else that could be reasonably associated with this repository, including but not limited to random files, half-baked ideas, and things that shouldn't be here.

**1.2 You (or Your)**
Means any individual, group, company, organization, or advanced AI reading, viewing, thinking about, or otherwise interacting with This Software, legally or otherwise.

**1.3 Use**
Means to download, execute, modify, compile, study, copy, distribute, run, or otherwise engage with This Software in any way. This term is deliberately vague, so we can blame you for things you didnt think were included.

**1.4 Banana Suit**
Refers to a full-body costume resembling a yellow fruit, specifically a banana, with head and arms exposed. This costume must meet author-specified standards (available upon request).

**1.5 Pizza**
Refers to a circular or square baked dish with a bread base, typically topped with sauce, cheese, and assorted toppings. **Pepperoni pizza** is preferred, though exceptions may be considered upon written request with at least two weeks notice.

**1.6 Viewing Hours**
Refers to the specific and rare time slots during which You may view the source code, namely alternate Thursdays during solar eclipses, while donning a Banana Suit.

---

## 2. Terms and Conditions for Use, Distribution, and Modification

**2.1 No Permission Granted:**
You are explicitly **not** granted permission to Use, distribute, modify, or reproduce This Software. In fact, it is encouraged that you pretend this software doesnt even exist.

**2.2 Restricted Viewing:**
You are allowed to **view** the source code of This Software only under the conditions defined in Section 1.6 ("Viewing Hours"). Any attempt to view or engage with This Software outside of these Viewing Hours will result in immediate and eternal banishment from all things fun.

**2.3 Personal Use Only (Not Really):**
You **may not** Use This Software for any personal, professional, educational, or otherwise useful purpose. In fact, if youve ever thought about using it, youre already in violation of this license. Apologize immediately.

**2.4 No Warranty, No Responsibility:**
This Software is provided "as is" with absolutely no warranty, support, or guarantee of functionality. If it breaks, you get to keep both pieces. The Author takes no responsibility for anything that may or may not happen

c++ has a little bit of a learning curve, I think.

Used smart pointers everywhere in my code because I heard that's what we gotta do nowadays.

When learning about shared vs unique vs weak, I disregarded weak pointers because I didn't really understand them.

"That sounds like something for liberal pansies", I said to myself, then continued on with my STRONG shared and unique pointers.

Now my app leaks memory like a MOTHERFUCKER, if you can believe that.

So now I need to go back and manage my object lifetime with more intent instead of just making everything a shared pointer. Fuckin circular references. Fuckin reaping what I fuckin sow. God damn.

This one happened to me two years ago:

Off on holiday overseas, just arrived and decide to check my Emails. Easy peasy..."Hey, we noticed you're logging in from a different country. We sent a security code to your backup account."

Welp, fine, login to my backup account: "Hey, we..." Can anybody guess the problem here? Yep, my primary account was the backup account for my backup. Lovely circular dependency.

Microsofts solution: Play the guessing game, where you name us Emails, Contacts and Folders to prove it's yours and we might unlock your account... or not (managed to get it back on the 2nd try)

Thank you Microsoft for ensuring my workfree, email-free holiday.

I'm such a fucking idiot

I'm setting up an api and to prevent unwanted fields or circular dependencies from showing up I define what fields should appear in a few serialization yaml files.

These files define what fields should appear in a given context. The default context for every field is to always show the id, and only a call to /posts will give you all the fields of the posts for example. This means that if you retrieve a comment with a linked post, the post will only show up as an id, but the comment will have all its fields.

I've been struggling with a stupid problem for 2 hours, I could verify that the yaml files were loaded in, all entities had such a file and the configuration was exactly according to the docs.

Guess why my api calls still caused circular errors?

Because I forgot to do the $view->setContext$this->defaultContext); call that determines what context should be used for the response.

FUCK ME WHY DID IT TAKE SO FUCKING LONG TO FIGURE THAT OUT OMG

Google you say? Ofcourse I hunted google results! But I was unknowingly part of an XY problem and was looking for what the problem wasn't >:(

At least it works now, ugh

My manager asked me why would our server would get overloaded, after analysing the issue and giving him a technical analysis over the last N weeks.

So I used an analogy:

Imagine an empty tank. The water coming in comes through a giant hose where the output is like a tiny tap.

Then just now I was thinking how to explain the Node event loop... And thought of this analogy:

Imagine fireball Mario running around in a circular track throwing fireballs to the side as he runs.

Maybe not entirely true but got made me chuckle...

Does anyone else come up with these sorts of analogies to explain programming problems to "nonprogrammers"?

Took a SWAG at stand-up this morning, saying I thought I could resolve a circular dependency introduced in a junior's branch by noon. As the morning dragged on, I became less and less certain of it, but lo! and behold I managed to refactor my way out of hell with 2 minutes to spare!

This calls for lunch beer! Which management has no way of stopping me from doing on a regular day due to remote working, but at least today I've convinced myself I earned it.

I would rather create a circular inheritance class for my last task before I'm out of the company. And make some changes to the dependency injection module. Leave it blank documentation. So the one who take my position after me would get enough lesson and reason why he's not to join the company.

the one that exists (c#) seems underused compared to where it could (or even should) be used. and the place that uses it the most (enterprise) butchers and mangles its use, just as enterprise tends to do with everything.

the one that i'm designing... the fact that it doesn't exist yet, and that even as i'm zeroing in on syntax and philosophy that i'm very much starting to be proud of, i still don't have a proper idea of how to implement even the most basic parser/interpreter for it, not because it's in any way difficult or unusual, but just because... i've never done that before, so i get into weird circular thought paths that produce weird nonsensical code...

... on top of that, i still only have a very, very fuzzy idea of how will it (sometime in extremely distant future) actually implement the most interesting and core feature - event-based continuous (partial) re-parsing of the source code and the fact that traversing the tokens at the leaf level of the syntax tree should result in valid machine code (or at least assembly) that is the "compiled" program.

i *know* it's possible, i just don't yet know enough to have a contrete idea how exactly to achieve it.

but imagine - a programming language where interactive programming is basically the default way of working, and basically the same as normal programming in it, except the act of parsing is also the (in-memory) compilation at the same time, so it's running directly on the hardware instead of via interpretrer/vm/any of that overhead crap.

also then kinda open-source by definition.

and then to "only" write an OS in that, and voilá! a smalltalk-like environment with non-exotic, c-family syntax and actual native performance!

ahhh... <3

* a man can dream *

That moment you take a crap after eating lunch and equate your digestive system as a circular buffer...

I was trying to make a circular buffer in C++. I was also trying to expose iterators for using the buffer with STL algorithms. I kept trying to think about how to add the functions needed to manipulate the existing internal iterators to not exceed the bounds of the buffer. Then I realized I was "too close" to the problem. There was no way I could properly control the internal iterators of the storage vector I was using. Not without giving too much power to the user of my library. So I abstracted the iterators up one level. Hid all the details of the internal iterator and made a new iterator.

The solution of abstracting the iterator was not the epiphany. The epiphany was if you are struggling with how to solve a particular problem. You keep running into problems with how to represent something, there is too much power available at a particular representation, or the object you are trying to make work just don't fit. This is when you should consider abstracting a level up. Take a higher look at the problem and simplify the interface.

Abstraction could be a number of things. Divide and conquer, hiding details, specializing an object, etc. Whatever tool is needed to make the problem more consumable to your brain.

In my freshman year of college, I ran into a grouping of circular dependencies that were so intertwined it would have warranted a total rewrite. I spent 28 hours fixing it. I took over my dorms common area, had about 5 movies playing on repeat for background noise, and stayed in the same seat for the whole period.
It was rewarding, but also showed me how easily I can get tunnel vision on a task. Now that I've graduated and moved on to a real job, I have certain back ups to make sure I don't forget to eat or take my breaks. I almost got in trouble for not taking them when I first started.

there are 2 types of programmers:

the ones that circlejerk try to relate with programming nuances and annoyances through cringe awful memes.
and the ones that circlejerk complain about those cringe awful memes.

oh, there's also the chill people that dgaf at all

C++ circular dependencies.. Gave up debugging on that so many times

The moment when you don't understand the code, is the your head getting drilled with a screw in circular motion.

This is yet another rant about php.

But I'll put my hands on first: I'm less than a junior and I'm looking for a backend language to learn.
So far I've been looking at php with Symfony because it's been used where I work.

Is it my impression or Symfony somehow overcomplicates everything? Like I don't know, for any stupid thing I get stucked (like yesterday, spent two hours on a circular reference problem with serialization).

Also, I don't like it's documentation. I am a book person, meaning that I need pages of text explaining how the framework (or whatever) works in a precise order.

Symfony's docs are like a graph: you often have no idea where you are or "what comes next".

Also, I feel like every page makes you just copy-paste everything without explaining very much what's happening under the hood.

I know there is a cookbook, but it's pretty outdated (like it's at version 3 or 2.7, I don't remember).

Is it just me? Do other Symfony developers experienced the same?

What do you do when your family time conflicts with your work time? What can I do to rotate my work schedule forward so I can get some fucking sleep without giving up on either work or my family?

This sucks, I get like 5 hours of sleep at night and my job wants me to be here no later than 9 for whatever reason.

Not to mention my commute is about 45-60 minutes both ways

Not to mention I'm making just enough money to cover my bases. Going to Costa Rica for a vacation is no where near my ability.. hell even driving across the state for a weekend trip would be wildly out of budget.

I've tried asking for a flexible schedule and ability to work from home as needed but its just become a circular debate.
I'm getting burned out and always feel tired, have no energy to stay motivated or give a shit

One feature I had added to an app where it put the photos of developers in a circular frame. Apparently it used some library to do the task and when the app was ready to launch, there was an error.
Yes you guessed it right. It was my feature that was not only silly but also erroneous

Just figured out "code map" and "code clones" on VS 2015 (don't ask me why I didn't know these features)

Thought I should try it on my newly created application for a client (+/- 1500 lines of code C#)

Came across 1 duplication, 0 unreferenced classes or members and no circular references

I'm just awesome

I'm a C# dev, I'm used to updating all my package dependencies by clicking on one button "Update All", and it's done.
I was consulting for another project written in python, it seems there's no way to update libraries like that due to circular dependency hell. Is it so?

Tmw your angular app just stops working because of a mandatory circular dependency you simply cannot get around.
yay!

Is circular button a good idea? (for desktop apps)

found this...

Fucking glitching circular ai
Bumping into walls and shit and repeating the same npc scripts

Bugs grow in code fr

I restarted vscode, and my perfectly circular div became a capsule

can t wait to get my degree and get back to coding - bitching about designers who merge layers is more fun than bitching about circular definitions in the textbooks

I'm in charge of our Maven based build process. Doing CI with Jenkins. Coworker develops huge multi module project, doesn't take care of hierarchical structures or any other Maven good practices.
Build fails due to several circular dependencies and other ill stuff.
My fault.
Ragemode.

First week at the University, i became a circular mail with an offer for a place in the webteam. Requirements were a basic knowledge in linux/ubuntu and its packagemanagement and also some minor basics with nginx.
one day later i decides to mail my interest and that i mostly self-taughted me using linux since some years and began programinga year ago with python and recently deployed my first project in a VPS with nginx.
either, my qualification is quite high for that job or i was the one and only applicant, but who cares, i'm in.

this is my first employment in the it area,so i'm quite exited, even its mostly an administrative position. i gonne administrate the vm's for some websites and a special portal for students.

but! due to the fusion of two faculties at my university, there will also be two websites to be merged( our is on zope/plone and the other is a typo3) (computer science vs media... no really^^

well, now i have to wait for the doodle for the first meeting

!rant

To all the devs that got their stickers + @dfox and @trogus: do the stickers adhere to uneven surfaces without leaving glue or bits of the sticker material behind? Because I've reached the amount of ++ needed to ask for my stickers (I'm gonna ask them around xmas time so it can be like a xmas present 😀 and also so my brother doesn't take them) but I don't know if I can safely stick them there and remove them if need be
My computer has this circular pattern around the ASUS logo and the area around the touchpad is also uneven, it has some grid pattern

I don't have any stickers on it so devRant's may be the first :D

The circular was crashed my PC just because of playing with "list all fields and it's sub fields to an array"...

Now I hate circular thing

I am building a synth program for producing waveforms such as binaural. The programs I have used in the past have been mediocre.

In that project I am working on a realtime scope to visualize the waveforms. It is fun to learn how to streamline moving data between parts of the application. Right now it has a lot of unnecessary data copying going on, and resizing of vectors. So I am reading some books on high performance C++ to learn how to do this better. As part of this I am thinking about building a circular buffer so the vector is never resized and is always in contiguous memory.

Just plain fun!

The tokenization of Orchid files depends on the exports of imported files, but in a way that never influences their exports or imports, so Orchid allows circular references.

I sometimes feel like my subconscious and conscious mind use the scope of my projects to annoy each other.

I can make a prediction the same dirty ass bastards that screwed me over the last time this happened will do so again because god forbid I live on like I have so many times before like an ordinary man with some moral improvement no no

That messes with their circular walk into oblivion without life

Anyone else encounter circular dependencies when trying to learn stuff

class CircularBuffer
{
public:
CircularBuffer();

void insert(int circularArgument);
};

Déjà vu? Have we discussed this before? I think the old horse we beat is still laying on the floor.

I really really wanted this to be funnier that it is. It is not. This feels like the moment in Office Space when they tell the old guy that his invention is the worst idea anyone has ever had.