Do you ever feel coding fatigue?

My dev mana has run dry, I've hit my rate limit.

That moment where your brain thinks "I should finish building this React project, it's good for my portfolio" or "I should really work on fixing this query performance issue, I already know what the problem is" — but your stomach churns at the thought of having to interpret even a single line of code?

The last few days it really does feel like a physical illness, a nauseated feeling whenever I open an IDE. I have written about 12 lines of code since Monday.

It goes beyond writer's block, it's not a lack of focus or inspiration, it's a big knot in my head of everything that's wrong and inconsistent in development, and it causes feelings of dread, desperation and revulsion when trying to wrap my head around the simplest stuff.

Does anyone have good tips to overcome this feeling, something faster and less savings-account-destroying than "take a sabbatical year and travel the world riding an emu"? (seems tempting though)

Devrant has a critical performance issue. It kills my performance. I believe more users can be affected

Wow... this is the perfect week for this topic.

Thursday, is the most fucked off I’ve ever been at work.

I’ll preface this story by saying that I won’t name names in the public domain to avoid anyone having something to use against me in court. But, I’m all for the freedom of information so please DM if you want to know who I’m talking about.

Yesterday I handed in my resignation, to the company that looked after me for my first 5 years out of university.

Thursday was my breaking point but to understand why I resigned you need a little back story.

I’m a developer for a corporate in a team of 10 or so.

The company that I work for is systemically incompetent and have shown me this without fail over the last 6 months.

For the last year we’ve had a brilliant contracted, AWS Certified developer who writes clean as hell hybrid mobile apps in Ion3, node, couch and a tonne of other up to the minute technologies. Shout out to Morpheus you legend, I know you’re here.

At its core my job as a developer is to develop and get a product into the end users hands.

Morpheus was taking some shit, and coming back to his desk angry as fuck over the last few months... as one of the more experienced devs and someone who gives a fuck I asked him what was up.

He told me, company want their mobile app that he’s developed on internal infrastructure... and that that wasn’t going to work.

Que a week of me validating his opinion, looking through his work and bringing myself up to speed.

I came to the conclusion that he’d done exactly what he was asked to, brilliant Work, clean code, great consideration to performance and UX in his design. He did really well. Crucially, the infrastructure proposed was self-contradicting, it wouldn’t work and if they tried to fudge it in it would barely fucking run.

So I told everyone I had the same opinion as him.

4 months of fucking arguing with internal PMs, managers and the project team go by... me and morpheus are told we’re not on the project.

The breaking point for me came last Wednesday, given no knowledge of the tech, some project fannies said Morpheus should be removed and his contract terminated.

I was up in fucking arms. He’d done everything really well, to see a fellow developer take shit for doing his job better than anyone else in [company] could was soul destroying.

That was the straw on the camels back. We don’t come to work to take shit for doing a good job. We don’t allow our superiors to give people shit in our team when they’re doing nothing but a good job. And you know what: the opinion of the person that knows what they’re talking about is worth 10 times that of the fools who don’t.

My manager told me to hold off, the person supposed to be supporting us told me to stand down. I told him I was going to get the app to the business lead because he fucking loves it and can tell us if there’s anything to change whilst architecture sorts out their outdated fucking ideas.

Stand down James. Do nothing. Don’t do your job. Don’t back Morpheus with his skills and abilities well beyond any of ours. Do nothing.

That was the deciding point for me, I said if Morpheus goes... I go... but then they continued their nonsense, so I’m going anyway.

I made the decision Thursday, and Friday had recruiters chomping at the bit to put the proper “senior” back in my title, and pay me what I’m worth.

The other issues that caused me to see this company in it’s true form:
- I raised a key security issue, documented it, and passed it over to the security team.
- they understood, and told the business users “we cannot use ArcGIS’ mobile apps, they don’t even pretend to be secure”
- the business users are still using the apps going into the GDPR because they don’t understand the ramifications of the decisions they’re making.

I noticed recently that [company] is completely unable to finish a project to time or budget... and that it’s always the developers put to blame.

I also noticed that middle management is in a constant state of flux with reorganisations because in truth the upper managers know they need to sack them.

For me though, it was that developers in [company], the people that know what they’re talking about; are never listened to.

Fuck being resigned to doing a shit job.

Fuck this company. On to one that can do it right.

Morpheus you beautiful bastard I know you’ll be off soon too but I also feel I’ve made a friend for life. “Private cloud” my arse.

Since making the decision Thursday I feel a lot more free, I have open job offers at places that do this well. I have a position of power in the company to demand what I need and get it. And I have the CEO and CTO’s ears perking up because their department is absolutely shocking.

Freedom is a wonderful feeling.

Our web department was deploying a fairly large sales campaign (equivalent to a ‘Black Friday’ for us), and the day before, at 4:00PM, one of the devs emails us and asks “Hey, just a heads up, the main sales page takes almost 30 seconds to load. Any chance you could find out why? Thanks!”
We click the URL they sent, and sure enough, 30 seconds on the dot.
Our department manager almost fell out of his chair (a few ‘F’ bombs were thrown).
DBAs sit next door, so he shouts…
Mgr: ”Hey, did you know the new sales page is taking 30 seconds to open!?”
DBA: “Yea, but it’s not the database. Are you just now hearing about this? They have had performance problems for over week now. Our traces show it’s something on their end.”
Mgr: “-bleep- no!”
Mgr tries to get a hold of anyone …no one is answering the phone..so he leaves to find someone…anyone with authority.
4:15 he comes back..
Mgr: “-beep- All the web managers were in a meeting. I had to interrupt and ask if they knew about the performance problem.”
Me: “Oh crap. I assume they didn’t know or they wouldn’t be in a meeting.”
Mgr: “-bleep- no! No one knew. Apparently the only ones who knew were the 3 developers and the DBA!”
Me: “Uh…what exactly do they want us to do?”
Mgr: “The –bleep- if I know!”
Me: “Are there any load tests we could use for the staging servers? Maybe it’s only the developer servers.”
DBA: “No, just those 3 developers testing. They could reproduce the slowness on staging, so no need for the load tests.”
Mgr: “Oh my –bleep-ing God!”
4:30 ..one of the vice presidents comes into our area…
VP: “So, do we know what the problem is? John tells me you guys are fixing the problem.”
Mgr: “No, we just heard about the problem half hour ago. DBAs said the database side is fine and the traces look like the bottleneck is on web side of things.”
VP: “Hmm, no, John said the problem is the caching. Aren’t you responsible for that?”
Mgr: “Uh…um…yea, but I don’t think anyone knows what the problem is yet.”
VP: “Well, get the caching problem fixed as soon as possible. Our sales numbers this year hinge on the deployment tomorrow.”
- VP leaves -
Me: “I looked at the cache, it’s fine. Their traffic is barely a blip. How much do you want to bet they have a bug or a mistyped url in their javascript? A consistent 30 second load time is suspiciously indicative of a timeout somewhere.”
Mgr: “I was thinking the same thing. I’ll have networking run a trace.”

4:45 Networking run their trace, and sure enough, there was some relative path of ‘something’ pointing to a local resource not on development, it was waiting/timing out after 30 seconds. Fixed the path and page loaded instantaneously. Network admin walks over..
NetworkAdmin: “We had no idea they were having problems. If they told us last week, we could have identified the issue. Did anyone else think 30 second load time was a bit suspicious?”
4:50 VP walks in (“John” is the web team manager)..
VP: “John said the caching issue is fixed. Great job everyone.”
Mgr: “It wasn’t the caching, it was a mistyped resource or something in a javascript file.”
VP: “But the caching is fixed? Right? John said it was caching. Anyway, great job everyone. We’re going to have a great day tomorrow!”
VP leaves
NetworkAdmin: “Ouch…you feel that?”
Me: “Feel what?”
NetworkAdmin: “That bus John just threw us under.”
Mgr: “Yea, but I think John just saved 3 jobs. Remember that.”

My colleges and I were talking about salaries in our company. Our team as about 10 members. Many of us are receiving interesting offers from other companies, and we concluded that we were being underpaid.

In this life, unless you ask to, no boss will raise you, even if you put some extra effort and work the shit out of you, to bring that profit, new client or something else good to the company.

Nobody was interested in talking directly about that to our manager. Just a side note, our manager is an awesome senior developer and a very nice guy. It shouldn't be too hard to talk about this issue to him.

I waited until our annual performance and salary revision to talk about it. Everyday our team talks about this. Everyone is going crazy.

So I went straight to the point, during this meeting with our manager, and said that we needed to be raised. All of us, because other companies were offering much better salaries.

He said to me: "Take this paper, write down what value should every one receive, including myself."

I took this opportunity and put down the values, raising about 600€ for each one.
I looked at it and said: "This looks ok. I'll will ask your colleagues to do the same task. Wait here."

So he went and requested everyone to do the same thing, without explaining why.

Guess what happened? Some mother fuckers actually cut on others salaries, instead of raising everyone equally.

Anyway the manager said he would show that to the CEO, and maybe something would happen.

We were all raised in the values I said so, because the CEO want us to be among the companies that pay the most.

After the backstabbing, no one ever talked about that. Except for 3 good fellow developers, that thanked me for my initiative.

We used to use Trello for our team boards and was starting to transition to Gitlab's issues for better code integration...

I became aware that my boss was being "demanded" to have a better analytics of our team performance so I started digging more insightful issue/tasks software like YouTrack ( Jetbrains ) and Jira ( Atlasian ).

After 2 months of trial and learning I suggested we go with YouTrack.

"We" are now using it for about 6 months already and it is a fucking mess.

My peers have no clue how to scrum, even after my efforts to teach them and they even spent a fucking 3 days workshop about it on fucking Google (!?!?) without me ( there is a rant about it ).

My boss is a nice person but the dude lacks any trace of competence to manage anyone other than him.

I'm tired of babysitting a man that is 10 years older than me and has a car that costs almost 10x mine.

I'm two days back from vacation and I almost rage quited 5 times.

I recently got mailed by our support department.

A customer using my program experienced performance issues after updating the whole system; attached is a video recorded by the customer clearly showing the difference.

I watched the video: the old version took 20 seconds to load. The new version 26. After querying the data, it's shown in a list.

The updated version showed 61 datasets instead of 6 in the old version.

I asked the supporter if he even watched the video and he answered: sure, and I'm able to see the performance issue!

Ah the day before launch of a new app. And right on schedule the businesses is attempting to completely alter their requirements including a COMPLETE OVERHAUL OF THE DATABASE MODEL TO ADDRESS AN ISSUE THAT HAS ALREADY BEEN FIXED. I wish they would share the drugs they are clearly on so I could also live in this dreamland delusion where you can turn something completely on its head right on the finish line and expect everything to go well.

Manager: Hey I think I have a solution to that performance we talked about last week

Dev: I already fixed it, it only takes 1 second instead of 30 now.

Manager: Ok but I’ve also figured out a solution. If we completely change the entire database model that one query could potentially be even faster according to my understanding of how databases operate.

Dev: I fixed it without the need for that, actually it was just a matter of better conc—

Manager: I think we should go with MY solution. Drop everything and restructure the database immediately! Be quick, as you know we launch this application tomorrow! Have an extra coffee today and just crush it out, don’t overthink this either just do it.

Dev: …

When you spend a few hrs hunting down a performance issue in your iOS app only to find that you accidentally hit the shortcut for "Slow Animations" in XCode. 😭😭😭

I worked once in a company which had this tourist app which should show places on map of the city. Unfortunately it slowed the App down to load more then a couple of places. Their solution was to limit the number of loaded places to teb and prohibited zomming out. I made it handle thousands of places at the same time. Main reason for the Performance issue was, that they sent all data they had about places big, big json objects with large text blobs) to the frontend. This part was easy, I instead sent only the data needed for the map like coordinates and icon type obviously. But still the backend struggeled hard with many objects from the DB, because they built a really shitty orm or what ever this was supposed to be: every line of data retrieved from the DB was immideatly wrapped in some class wich direved from another class which had some magic methods in it which caused some absurd loops over all other obejcts and even more DB queries in unexpected moments and also in the fucking constructor. So it turrned out that the map issue was only the top of the iceberg, since using any data from the DB was extremely expensive. The hard part was to understand the insaness of this abnormination and find the bottlenecks.

Found this gem of a comment in a code base written 4 years back.

/*
Invoke <Service Base URL>/asset/v2/details/<SN> to get asset details
Feeling very bad to include this call, but we really need to use this !!!
This call is gonna take ~20s to respond. I've even increased the overall timeout of this module, just for this call !!!
So, if you are looking to debug any performance issue, I wish you jump directly here,
remove this call and just use master data management (MDM)
P.S: It is not that simple, as MDM and this asset DB (both asset masters) has differences in how the asset is defined :(
*/

Still trying to understand how to remove this costly time-consuming call and replace with an efficient one !!

And, of-course, the original author left 2 years back :(

Boss: we have to fix this bug.
Me: It is not a bug ..the server takes more time to send the response which cause the timeout issue . we may need to change the implementation to increase the performance to send the response quickly. It will take some time
Boss: okay can we fix this by today
Me: ya if we increase timeout to 20 seconds the issue is fixed
Boss: No we want the server to send the response quickly and we need the fix now

I worked for the weekend to fix it finally......Guess what ....the change dint go live since the scenario was not valid and will never likely to happen in production

So I wrote an application that loads data from a 3rd party API. It allows the user to enter a record locator number and pull it up. By design, the value can be a partial match and it will pull up the record still.

The first API call I make only took 2-3 seconds, so I didn't see an issue as it's loading most of the data the app needs. I keep the filters/fields as they are and move on.

Fast forward 6 months. The user is complaining that the records are taking 30-45 seconds to load. Sure enough, load times are terrible. I've made lots of changes to what fields I'm loading through the API, and I'm calling several additional APIs, so I start pulling pieces of code out to see if anything improves. They all barely make any difference--still 30+ second load times. I end up removing everything except the first API call I developed that was taking 2-3 seconds before. Still taking 30+ seconds.

The 3rd party API allows you to filter using "starts with" or "contains". I used "contains" initially and had no issue, but I decided to try "starts with" since it should fit most use cases.

Load time is less than one second. I add back everything else. Load time is just over a second.

It seems that the 3rd party updated the API and multiplied load times by 10 when using that particular filter. I spent almost an hour on this since the platform doesn't support performance or debugging tools very well, and it all came down to a one line fix.

So today, again, I discovered the importance of unitests.
I was solving this performance issue, in which we had a few update actions for multiple entities in mongo, but it took FOREVER to complete, even when I unified it into one bulkWrite command.
Since the unified write did improve performance slightly, and we wanted to move on, we decided to let this bug go.
So there I was committing my changes when I got a rejection from the pre-commit hook since I didn't have enough unitests coverage.
Ok, let's start writing some unitests.
Some unitests also needed to test the bulk write. So there I was comparing expected with actual result, and suddenly I got a huge facepalm.
Apparently some rogue for loop iterated all entities again for each entity that needed update. So instead of getting one update per entity, I got N identical update commands per each of the N entities 🤦‍♂️
Needless to say, fixing this fixed the performance bug entirely.
Thank you unitests and pre-commit hooks!

Still dealing with the web department and their finger pointing after several thousand errors logged.

SeniorWebDev: “Looks like there were 250 database timeout errors at 11:02AM. DBAs might want to take a look.”

I look at the actual exceptions being logged (bulk of the over 1,600 logged errors)..

“Object reference not set to an instance of an object.”

Then I looked the email timestamp…11:00AM. We received the email notification *before* the database timeout errors occurred.

I gather some facts…when the exceptions started, when they ended, and used the stack trace to find the code not checking for null (maybe 10 minutes of junior dev detective work). Send the data to the ‘powers that be’ and carried on with my daily tasks.
I attached what I found (not the actual code, it was changed to protect the innocent)
Couple of hours later another WebDev replied…

WebDev: “These errors look like a database connectivity issue between the web site and the saleitem data service. Appears the logging framework doesn’t allow us to log any information about the database connection.”

FRACK!!...that Fracking lying piece of frack! Our team is responsible for the logging framework. I was typing up my response (having to calm down) then about a minute later the head DBA replies …

DBA: “Do you have any evidence of this? Our logs show no connectivity issues. The logging framework does have the ability to log an extensive amount of data regarding the database transaction. Database name, server, login, command text, and parameter values. Everything we need to troubleshoot. This is the link to the documentation …. If you implement the one line of code to gather the data, it will go a long way in helping us debug performance and connectivity issue. Thank you.”

DBA sends me a skype message “You’re welcome :)”

Ahh..nice to see someone else fed up with their lying bull...stuff.

So at the old job, i needed support for an issue relating to Amazon S3. We used a third party Python plugin for sending files to our buckets, but had some pretty severe performance issues when trying a 2-way sync.
Naturally, I sought help on StackOverflow, and was asked to share my config. Without much thought, I pasted the config file.
Next comment made me aware that our API id and key was listed in this config (pretty rediculous to keep such private info in the same file as configuration, but oh well).
I edited my question and removed the keys, and did not think about the fact that revisions are stored.

Two weeks later, my boss asks me if I know why the Amazon bill is for 25.000$ when it used to be <100$ 😳

I've never been so scared in my life. Luckily, Amazon was nice enough to waive the entire fee, and I leaned a little about protecting vital information

I was assigned the research of an issue, after doing that I told in a meeting what we needed to solve, then someone asked which engineer would take care of that so I said me and they didn't listen. Then they asked again and someone else spoke before I could. I can't have good performance if they don't give me tasks. I'm bored of doing nothing, fuck quarantine making people forget I exist.

Nvidia at it again. After receiving backlash for trying to pass off a 4070 as 4080/12GB, und "unlaunching" it, they did the same shit again.

This time with a 3060/8GB. Yes, as RTX 3060, a well established product with a lot of reviews, intentionally misleading the customers who think that a 3060 is always the regular 12GB model. And the new shit isn't even cheaper.

The main issue isn't the reduced amount of VRAM, it's cutting down the memory bus from 192 to 128 bits, that costs quite some performance.

So if you see a 3060 and think it might be a bargain, watch out that you don't accidentally end up with the "bait and switch" 8GB model.

Or even better, consider a 6650 XT that is both faster and cheaper than a 3060, and RT is lackluster on the small RTX cards anyway.

We have a badly out of shape but functional product , the result of a "if its not broke don't fix it" mentality. The only thing manangement cares is our next release and making meetings to plan other meetings...

Now comes the time of the security Audit (PCI)...

Manager : oh noooo the audit will fix this issue, quickkk fix it !

Us : welllll its a lengthy process but doable, we just gotta do a,b,c,d,e . Part a is essentially what we need the rest are refactoring bits of the system to support part a since the performance would be shit otherwise

Manager: can you do part a before the audit starts ?

Us: yep.

Manager: do it . Oh and pop those other issues on JIRA so we can track em

Audit completed....

Manager: so we got through ok?

Us : 👍 yep

Manager: okayy, take those other issues..... and stick em at the bottom of the back log...

Us : huh ? *suspicious faces*..... okay but performance is gonna be poor with the system as it is cuz of part A....

Manager: yeaaahhh * troll face* ....about that.... roll it back and stick that too at the bottom of the log. We got to focus our next release. Lemme schedule a meeting for that 😊

Us : faceplam

Depressed since yesterday.

Updated all our clients Dialers. Stellar performance. Suddenly one of 15 can’t hang up three way calls.

It’s one of our biggest clients. And they just started. We upgraded the dialers so the answering machine detection would improve for them and it did, along with vast performance upgrades as well. Suddenly, this issue.

2 days in they pull the plug until we fix it. The issue is sporadic and we cannot reproduce. No one else is having the issue. I can’t even debug it properly as it’s a third party dialer with no customizations on it. I found out where the error is, but no idea the workflow they got it to happen with or why. It’s so frustrating. It happens using the dialer native interface, and our integration via api calls. The channel doesn’t get sent to the command for some random reason, and only sometimes.

So even if it’s fixed they don’t trust the system. Now they are losing the full integration we have with the crm and dialer and it’s going to be a mess of data for them. All because of this one issue. They love the CRM though...

If they had just stayed on one more day I’m sure I could have found it. Now I have to play forensic scientist and look through old data, without being able to see the client code that was causing the issue.

Just threw some cash down to be able to talk to the dialer engineers and hopefully see what’s up. What a nightmare. And I have so many other projects for the platform due so soon...

Sigh. Super depressing.

This might not resonate with many ranters here... but FUCK Taylor Otwell & Graham Campbell.

Like, not on a personal level. Maybe they're great to drink a beer with. But as framework devs... fuck everything about them.

Laravel seems so nice, it takes away many annoyances of developing in PHP. Collections are the array object you've always needed. The route bindings, middlewares, request validation objects, it's all sweet.

But eventually your company serves a few million customers, you run into specific performance problems or missing features on a deeper level. You open the issue tracker... and see a few hundred issues about the problems you are encountering, they already exist.

Some just have a short paragraph with a request for a feature, some complete PRs with tests in the style of the framework. All of them closed.

Reasons?

"We don't think anyone will ever need this"
"This seems complicated, you can just do <super non-DRY hacky code>"

FUCK YOU WITH YOUR TODO APP SNIPPETS AND USER-POST-ARTICLE EXAMPLES. I'M NOT BUILDING THE NEXT WORDPRESS. I'M DEALING WITH THE REALITY OF GRAPH DATABASE CLUSTERS, COMPLEX AUDITING LOGS AND A GAZILLION QUERIES PER SECOND.

Sigh... the problem with all these "simple" and "elegant" languages & frameworks is that they don't fucking scale.

Not because the language, server or framework intrinsically can't do it, but because the maintainers are stuck thinking in terms of their retarded non-realistic example apps.

I think I'll go back to my cave and write some Haskell or Rust to calm down.

Can someone help me understand?

I subscribed to a nifty IT-releated magazine, and on its back, there's an ad for "Dedicated root server hosting", nothing unusual at a first glance, but after I read the issue, I decided to humor them and see what it is that they offered, and... It just... Doesn't make sense to me!

An ad for "Dedicated Root Server" - What is a dedicated root server first of all? Root servers of any infrastructure sound pretty important.

But, the ad also boasts "High speed performance with the new Intel Core i9-9900K octa-core processor", that's the first weird thing.

Why would anyone responsible enough want to put an i9 into a highly-reliable root server, when the thing doesn't even support ECC? Also, come on, octa-core isn't much, I deal with servers that have anywhere between 2 and 24 cores. 8 isn't exactly a win, even if it has a higher per-core clock.

Oh, also, further down the ad has a list of, seeming, advantages/specs of the servers, they proclaim that the CPU "incl. Hyper-Threading-Technology"... Isn't that... Standard when it comes to servers? I have never seen a server without hyperthreading so far at my job.

"64 GBs of DDR4 RAM" - Fair enough, 64 gigs is a good amount, but... Again, its not ECC, something I would never put into a server.

"2 x 8 TB SATA Enterprise Hard Drive 7200 rpm" - Heh, "enterprise hard drive", another cheap marketing word, would impress me more if they mentioned an actual brand/model, but I'll bite, and say that at least the 7200 rpm is better than I expected.

"100 GBs of Backup Space" - That's... Really, really little. I've dealt with clients who's single database backup is larger than that. Especially with 2x8 TB HDD (Even accounting for software raids on top)

This one cracks me up - "Traffic unlimited"
Whaaaat?! You are not gonna give me a limit to the total transferred traffic to the internet for my server in your data center? Oh, how generous of you, only, the other case would make the server just an expensive paperweight! I thought this ad was for semi-professionals at least, so why mention traffic, and not bandwidth, the thing that matters much more when it comes to servers? How big of a bandwidth do I get? Don't tell me you use dialup for your "Dedicated Root Server"s!

"Location Germany or Finland" - Fair enough, geolocation can matter when it comes to latency.

"No minimum contract" - Oooh, how kiiiind of you, again, you are not gonna charge me extra for using the server only as long as I pay? How nice!

"Setup Fee £60" - I guess, fair enough, the server is not gonna set itself up, only...

The whole ad is for "monthly from £55.50", that's quite the large fee for setup.

Oh, and a cherry on top, the tiny print on the bottom mentions: "All prices exclude VAT and are a subject to..." blah blah blah.
Really? I thought that this sort of almost customer deceipt is present only in the common people's sphere!

I must say, there's being unimpressed, and then... There's this. Why, just... Why? Anyone understands this? Because I don't...

funny coincidence happened at work the other day.
One dev ask to get more ram for his pc so we sent him a link to download more ram... after all the laughs we actually gave hom more ram.
The next day, we had performance issue on our dev servers, and after checking the VM's where missing 4gb of ram each from the original setup... so i poke my dev and say see now we know where the downloaded ram came from XD. man those small things really make my day

How can I make my manager understand that performance should not be measured by how many tickets we have resolved?

If the ticket is an easy one then sure 1-2 days is enough, but for some complicated shit or dealing with models that I have never touched before, I am gonna need several days just to understand the requirement.

For some fucked up reason, our story point is in hours, instead of days. So when we say 24 hours, then it's only 3 days.

Another fucked up reason is that my colleagues doesn't seem to mind. I am the most vocal one objecting when got assigned too many tickets. They just joke around and seem to accept it.

FYI, I am just 6 months in and bouncing between 3 projects.
Am I just too lazy or slow?
In my previous company, the devs seemed to be pretty chill, and the project manager only complained when an issue has been dragging on for weeks.

So fuck this. Fucking fuckers fuck this.

We've been having massive performance issues with a nested drag and drop component. I built this abomination about a year ago and had to rush through it due to my colleague not thinking the change was necessary, even though the previous revision was even worse. It's been going strong for a while, but since a month ago it has started to perform badly. Makes sense, because it was hacked together, and wasn't made for the amount of data that it's handling now.

So the other day I presented the issue to my colleague, telling him exactly what the problem was, and that we'll have to rewrite quite a bunch of the code to get it working. Today when I bring it up again he is really negative towards the changes because they are so big, and don't really want me to do them. He is, however, super stressed about the performance issues and starts digging around in the code himself. Code that he's never touched, don't understand how it works, and has said he's not interested in learning about. He even says he sucks at frontend and Vue himself. So we sit there from morning to lunch, digging through the code together (I had to do it as well because he came nowhere). And what do you think the conclusion was? The same thing I told him a few days ago.

So what now then? He still don't want me to do the changes, but still wants it solved! How the fuck is that supposed to happen?!?

Worst part is that we're the only two developers in the company, and our boss has little IT experience. That puts me and my colleague at the same hierarchical level, so all decisions has to be cool with the both of us.

So fuck this. Fucking fuckers fuck this.

“We mob every thing so that means we don’t need pull requests, because by the time the code is committed it’s had plenty of pairs of eyes on it”

Well, I beg to differ.
Today I read through some of this spaghetti mobbed code to look into a performance issue. Wasn’t supposed to but bored stiff so I ‘went dark’ and did it without the mob.

After about an hour I figured out it runs a few lines of dubious code and if there’s an error it tries many times over with an exponential back off.
And each run of the methods will fail for sure because of how it’s written.
Someone must’ve seen this problem but instead of realising it can never work, they’ve wrapped it in retries and back offs.

So many back offs and retries that it just sits there doing this for 25 minutes.

But yeah. The mobbing works great guys, keep churning out this quality code. 😂😂😂
Can’t wait to see the back of this joke job.

After a week of logs investigation, we finally found a solution for performance issue. Just scaled up the app vertically to the next tier plan in Azure.

So finally i said goodbye to ubuntu forever but I stayed on debian have installed and setup crunchbang its performance is much better and this os is so lighter.
my wifi issue is fixed here didn't do anything at all. I'm loving this os
thanks all those guys who tried to help me fix wifi issue

I need to convert lots and lots of lengthy hard-coded entities into backend objects, as I'm tired of pushing new commits every time something superficial needs to change.

Also, I need to figure out continuous integration. The guy who was going to help with that just left the company, and I was using his eventual forthcoming help as an excuse not to take responsibility for learning about it myself.

I need to learn golang and start converting some code to it, to see if the performance compares to the perl that's currently in place. Perl is brilliant, but aside from me, only old people know it, at my office. That definitely creates a longterm supportability issue.

debugging a performance issue. basically the original dev had no idea what a database was for. system was generating millions of buffered reads, and paging horribly.

to see if an id existed they had done the following:
fetch all 1 million rows into an array.
iterate the array looking for a match.
if found, set found=true
continue to iterate the rest of the array.
return found.
repeat at every login.

replaced with
return person.get(id)

set world record for most i/o avoided with one liner.

when you realize that performance issue you just could not figure out is the SYS admin taking a full back of your production machine during peek traffic hours

Been struggling with a performance issue for weeks, been writing a search engine (or sorts) for internal company use only. Discovered the locations that are being indexed contain a directory used for back up purposes that contain archives of everything inside it.

Wrote a means to exclude these directories, performance improves up to 1600% (top end, sadly, not across the board) feel freaking awesome.

Boss acts like I've just pull Atlantis off the floor with my teeth.

It was a two line change, I wish the really difficult tasks were treated this way and not with "oh it shouldn't take you long!"

I got randomly PIP’ed by this small company I was working at. They claimed performance issues without referring to specifics so I’m sure it was a financial issue (I’m paid more than other devs). So I took the laptop home and claimed I broke my back and started working from home (they don’t appreciate WFH). I did this so that I can freely give interviews. And now after 2 weeks I got 4 offers (with more than 50% hike). I’ve started the necessary documentation work and communicated my last working day with my current company.

So what is the moral of this story? Creative comments only.

It is approximately 42 degrees C outside. And guess whose fucking compressor just went to shit? Mine. Fucking piece of shit. I absolutely fucking hate this shit. Finding the time to go to the shop is pointless when I can fix it myself, but IN the fucking event that the compressor is actually faulty and needs to be replaced then I would have to struggle to wait for the fucking part to get here. If my luck permits and this is an issue that is fixable through a simple relay change then fucking hooray.

But I know how fucking shitty my fucking luck is and its going to fuck me in the ass probably. I will troop through the heat, no problem, but I am the one that carries my 2 year old daughter everywhere and I am not about to put her through that bullshit.

So I call my wife and explain to her the situation, I don't need for her to do fucking anything, I can take care of it myself, but I tell her NOT to have me go out on random bullshit with the girl while the car is like that, I did it to make her understand beforehand because every day is an additional 1 and a half hours of driving around the city to take her do bullshit. I told her that in the event of me needing to go pick something up then it would have to be after the fucking sun goes out(which in this fucking bullshit ass town it happens after fucking 7 or 7:30pm) and she would have to stay home with the girl. What does she do? she gets upset. Of course she got fucking upset. Like if I need that fucking bs right now. OH and my fucking main Linux machine is apparently having battery issues.

OAN my manager gave me my performance review yesterday. The she made are outstanding and my score is perfect. The board is going to give a raise to everyone of us that got an high enough score so that got me in a good mood. I am holding on to that feeling before I lose my shit. Every single fucking time some bs puts me in this mood I am constantly wishing that a motherfucker would.

Fucking bullshit man. Can't have a FUCKING break anyfuckingwere.

This just in on an episode of Murphy's fucking law.

Happend a few months ago...

We encountered a performance issue somewhere in our Code, written by a guy who already left.
It was kind of this:

foreach(var id in idList)
{
CallServiceWithDataBaseAccess(new List<string>()
{
id
}
}

Well. It was obvious as in this example...

everytime i buy a new phone ,i feel this sense of extreme regret :(

i bought a moto g 5g phone last year in feb, it was so good . it didn't had any out of the world cameras or some funky stuff, but it gave a decent performance and i couldn't want any other phone.

In October my mom's phone started giving issues so i bought a realme phone for her that was half my phone's price. i couldn't spent any mor e because otherwise she wouldn't take it. she accepted the cheaper phone and within 4 days sue was cursing it. the phone had decent specs but would lag in certain apps like zoom, and won't run some call recorder apps. at the end i swapped my phone with mom's since i didn't cared about zoom or the recorder.

now this shit realme phone's memory has gone around 60% full of my stuff, and its showing its limitations. this shit auto relaunches insta after a few minutes of usage, probably because its runtime memory gets short( 4gb 128gb device gets memory shortages. nice). its video quality is shit and camera also takes rarely good pics.

the worst thing i like about smartphones today is how they over optimise the ui. this insta issue and auto call recorders not working is simply because of the realme skin running over the stock android. i had similar issues with a xiaomi device i bought for my dad sometime ago. (fortunately my dad is more medieval so that crap has not came back to me :'/ )

so overall i am buying a 3rd phone in 17 months.
This time it's Samsung f23 and am worried that it's also going to suck. i was this 🤏close to buying a pixel 6 or even an iphone coz i can afford them.

but the regret of buying such an expensive phone that will need replacement in 2 years made me rethink.

the only android os that have suited me the best is stock and as of now only 2 companies are making it : google and moto(* it's 100% aosp with 3 extra apps but they can't say that, so they also state that they are not stock os) . one plus is also a brand that i have heard makes a good os . but recently i also heard that they have completely scrapped their os and using oppo's softwares . plus the amount of tickets we get for notifications not working in oneplus, am sure their optimization is extremely aggressive.

so everything between a moderate price phone ( that will need a replacement in 2 years ) to a flagship felt unnecessary to me, so i went ahead with a Samsung's shit phone. f23 has almost same specs as moto but it's again a heavily customised os. i wanna waste my money on trying a custom os and declare it shitty.

most of my friends that use Samsung are fan of it but they are also not very techy so i guess it suits them well. i am the guy who first installs nova launcher in his device, so let's see what it brings on the table. from the 3rd person p.o.v, i felt its screen and camera images to he nice whenever i used their mobiles, so let's see what this brings to the table :(

TL;DR: TIL for heavy queries use PDO and not some frameworks DB class

ffs I was trying to save 300k+ lines at once with Laravel for weeks. Mind you from a text file. 1gb ram on the vps so while trying to prepare the text to save: Fatal Error: Allowed Memory Size of bla bla Bytes Exhausted

ok so lets put it in a loop: Fatal error: Maximum execution time of 30 seconds exceeded (set_time_limit(0); lol)

optimising, varying the code got me into a situation when the content got saved in the BD but inconsistent (duplicates) and the table had often more than 1,5M rows. That was what told me its not a performance issue, my code is the issue. (dah)

I was starting to think it would be easier to export a prepared query to a sql file and load the file into the db as thats the fastest possible option...I even started to think about switching to python, then it hit me, Laravel has a shitload of routes to the DB so I switched to PDO

benchmark on 1vCPU, 1GB RAM VPS with SSD
379k lines with 11 columns in less than 10 sec with a loop of saving every ~6000 rows (if i tried choking it to save the whole thing at once it went up to 16-17sec)

So, I produce a monthly report for our customer service department each month, and this report includes various statistics related to our company's support performance. Two of the included statistics are the "Average Speed of Answer" (ASA for short) and the "Abandoned Call percentage" (ABD % for short) that are derived from client calls to support.

The formulae for these values are:
- ASA = time in seconds all calls that were answered spent waiting to be answered divided by the number of answered calls - displayed as hh:mm:ss

- ABD % = number of abandoned calls minus those that were abandoned in under 10 seconds (referred to as "short abandoned") divided by the sum of total calls that were offered minus the sum of short abandons & transfers

These statistics are also included in a daily version of the same report that all Customer Service leadership personnel have access to.

Now, every single fucking month the same Sr. Manager always has some kind of "discrepancy" with the monthly report that ALWAYS boils down to his dumbass trying to average shit on the daily Excel reports for that month and it being different than what the monthly report is showing. Now, these reports ONLY display the calculated value for any calculated fields mind you - not the raw values of the DB fields used in said calculations.

This month I have to tell this shit-for-brains that you can't just take an average of ASA & ABD % from the Daily's and compare them to the Monthly numbers because their calculated fucking fields!!!

Come to think of it, this has been his issue for like the past 5 months, and I seriously can't fix stupid!

Sometimes I just wanna reply to his snarky ass, corporate bullshit emails like, "BRUH!, The only motherfucking discrepancy I can locate is your IQ and your fucking title - that shit don't correlate homie! Need to take that ass back to High School statistics or something!"

But I digress...

TL;DR
I have to deal with a Sr. Manager who doesn't fucking realize you can't average a calculated field from a daily report and think it's gonna match up with the monthly report. I believe he is borderline retarded, and I often wonder how he got the "Sr." In his title let alone "Manager".

Oh wait, this is corporate America - you just gotta kiss the most ass... never mind.

Since the issue is within the legacy backend data, this brings us the great opportunity to solve and sanitize the data on the frontend and therefore killing the performance of the application! Sincerely, a manager that doesn't give a shit

Was trying to figure out why my fix had created a performance issue in our app. Tried loads of different things. Turned out it was because I was iterating over a ~300 item array, and then iterating over another ~300 item array within that loop 😂

300 iterations * 300 = unhappy iPad

I was told I have to integrate my current project for my current group with my first group's baseline. W/e. As long as I get paid.

Well the issue is, I haven't been with that group in a year and a half. And their product, I now realize, is terrible. I better get a great fucking performance review.

1) Had to fix severe bugs in a dynamic UI (configuration-driven forms) component.

Recognized undocumented Copy/Paste/Modify/FuckUp driven variations of the same component all over the project. Unsurprisingly, the implementations covered 99% of the antipattern catalog on wiki.c2.com and could compete with brainfuck in regard to human-readable code.

Escalated the issue, proposed a redesign using a new approach, got it approved.

Designed, Implemented, tested and verified the new shared and generic component. Integrated into the main product in the experimental branch. Presented to tech lead/management. Everyone was happy and my solution opened even more possibilities.

Now the WTF moment: the product with the updated dynamic UI solution never has been completely tested by a QA engineer despite my multiple requests and reminders.

It never got merged into baseline.
New initiatives to fix the dynamic UI issues have been made by other developers. Basically looking up my implementation. Removing parts they do not understand and wondering why the data validation does not work. And of course taking the credit.

2) back in 2013, boss wanted me to optimize batch processing performance in the product I developed. Profiling proved that the bottleneck ist not my code, but the "core" I had to use and which I must never ever touch. Reported back to him. He said he does not care and the processing has to get faster. And I must not touch the "core".

(FYI: the "core" was auto-generated from VB6 to VB.Net. Stored in SourceSafe. Unmaintainable, distributed about a bunch of 5000+ LoC files, eye-cancer inducing singlethreaded something, which had naive raw database queries causing the low performance.)

I needed to align instruction execution to a 64bit boundary, for custom CPU architecture that I'm building. Basically the ISA had 3 types of instruction lengths; 16bit, 32bit, and 48bit. The core did 64bit fetch from the Instruction Cache, the issue was that if an instruction was in between two blocks of data I needed to fetch two blocks. That would impact performance a bit. So I had to modify GCC sources of the ISA that I'm using. So instead of doing it the right way, I just did it the lazy way and modified the GCC backend to print

.p2alignw 3, 0x00ff, 4
.p2alignw 3, 0x00ff, 2

On each 48bit and 32bit instruction to generate NOPs. And it did work lol.

Me (to peer): I counted all of the items in the list, and if the list count is zero, we branch to this logic.

Peer: I don't like that, and reject your PR. You should get the list of items, and check to see if the list is empty.

- How is that fucking different than what I did?

- This is not a performance issue, we're talking less than 20 milliseconds on a command run three times a day by developers, not customers.

I had a pretty good year! I've gone from being a totally unknown passionate web dev to a respected full stack dev. This will be a bit lengthy rant...
Best:
- Got my first full time employment dev role at a company after being self-taught for 8+ years at the start of the year. Finally got someone to take the risk of hiring someone who's "untested" and only done small and odd jobs professionally. This kickstarted my career, super grateful for that!
- Started my own programming consulting company.
- Gained enough confidence to apply to other jobs, snatched a few consulting jobs, nailed the interviews even though I never practiced any leet code.
- Currently work as a 99% remote dev (only meet up in person during the initialization of some projects.) I never thought working remotely could actually work this well. I am able to stay productive and actually focus on the work instead of living up to the 9-5 standard. If I want to go for a walk to think I can do that, I can be as social and asocial as I want. I like to sleep in and work during the night with a cup of tea in the dark and it's not an issue! I really like the freedom and I feel like I've never been more productive.
- Ended up with very happy customers and now got a steady amount of jobs rolling in and contracts are being extended.
- I learned a lot, specialized in graph databases, no more db modelling hell. Loving it!
- Got a job where I can use my favorite tools and actually create something from scratch which includes a lot of different fields. I am really happy I can use all my skills and learn new things along the way, like data analysis, databricks, hadoop, data ingesting, centralised auth like promerium and centralised logging.
- I also learned how important softskills are, I've learned to understand my clients needs and how to both communicate both as a developer and an entrepeneur.
Worst:
- First job had a manager which just gave me the specifications solo project and didn't check in or meet me for 8 weeks with vague specifications. Turns out the manager was super biased on how to write code and wanted to micromanage every aspect while still being totally absent. They got mad that I had used AJAX for requests as that was a "waste of time".
- I learned the harsh reality of working as a contractor in the US from a foreign country. Worked on an "indefinite" contract, suddenly got a 2 day notification to sum up my work (not related to my performance) after being there for 7+ months.
- I really don't like the current industry standard when it comes to developing websites (I mostly work in node.js), I like working with static websites (with static website generators like what the Svelte.js driver) and use a REST API for dynamic content. When working on the backend there's a library for everything and I've wasted so many hours this year to fix bugs and create workarounds related to dependencies. You need to dive into a rabbit hole for every tool and do something which may work or break something later. I've had so many issues with CICD and deployment to the cloud. There's a library for everything but there's so many that it's impossible to learn about the edge cases of everything. Doesn't help that everything is abstracted away, which works 90% of the time but I use 15 times the time to debug things when a bug appears. I work against a black box which may or may not have an up to date documentation and it's so complex that it will require you to yell incantations from the F#$K
era and sacrifice a goat for it to work properly.
- Learned that a lot of companies call their complex services "microservices". Ah yes, the microservice with 20 endpoints which all do completely unrelated tasks?

"as well as stability and performance improvement" aka revert the stupid address bar change that requires an extra click to actually edit the text.

Yes Google must've thought people were idiots to have to show a copy button by default and an extra button to edit the link...

Oh wait they must've realized actually they're the idiots. I actually used Firefox for a while but their tab manager with the square grid is annoying or some other issue...

Tl;Dr:
The new windows subsystem for Linux might severely slow compilation time for me.

Microsoft is releasing a preview of WSL 2 which works fundamentally different to WSL 1, which I currently use.

For those who don't know, WSL (or Windows Subsystem for Linux) used to be a compatibility layer, which "translated" Linux syscalls to Windows syscalls. This enables the execution of Linux applications on Windows. The new WSL (WSL 2) doesn't do any of that, instead, it is a highly optimised Virtual Machine.

So don't get me wrong from a performance point of view there is no Issue, RAM and CPU usage is truly astonishingly small and performance of Linux applications is much improved over WSL 1.

BUT, apparently, accessing files stored on Windows through Linux is now piss slow.

Great, truly outstanding.

Why is this a problem? Well, I use WSL to develop c++ Linux applications using CLion, the way this works is that you set up an ssh server in WSL, which CLion uses to do compilations.

One _needs_ to have the project files stored on Windows as otherwise CLion on Windows can't access them.

If I wanted a Linux VM I would have installed one.

Urgh.

Up until now, I never had any breaking updates on Linux on my laptop, Except for Nvidia drivers stopping. It would switch to noveau. Even my cobbled together hack of Broadcom Bluetooth solution worked without even having to touch it. Well, I still don't have problems with core Linux but add gnome to the issue mix today. Surprisingly, Nvidia drivers for the first time Nvidia drivers upgraded (to 340) and I didn't had to do anything for it to work. Gnome deprecated synaptics driver support and now uses libinput implementation for it. Well Ubuntu Gnome updater won't clean the configuration and I had to remove the driver and clean config myself. Nothing too much, i have to deal with these stuff on my arch installation but Ubuntu has been "it works fine. No need to interfere" thing for me. It works fine on Wayland (it always used libinput on Wayland a if I am correct) but nvidia drivers doesn't support Wayland. And then since the update gnome has been disabling some of my extensions at random. All on X. I have no problems with Wayland except for Nvidia fucking drivers. All that said, its still better than windows where I lost fucking network connectivity during something important. And the trackpad drivers on Linux are somehow much better than anything I have used on windows. (that or Sony made fucking great trackpads and nobody noticed). Here's to hoping Nvidia starts supporting drawing on Wayland and I can ditch X completely. I have seen visible improvements in performance under load and slight decrease in battery usage with Wayland.

so my poor old hp bro is starting to give up on me after 3 years . there are both battery and performance issues. I knew its death was near when i got its keyboard replaced i saw its battery's state 6 months ago. it was fat as me . Now it can't live without the wire for more than 30 mins.

apart from that am getting frustrated with everyday performance of my system. all i open is 50 tabs of chrome and android studio where bitch gradle generates a billion byte sized files at million places and cache folders . (and sometimes a terminal and/or files and/or vscode).

I have decent specs tho i5 7th generation/8gb ddr4 ram/ 2gb nvidea graphics/ 1tb hdd. but still my ubuntu gets stuck everytime i switch between chrome and AS . (maybe i have not made correct swap partitions or maybe there is an issue due to ubuntu/windows dualboot)

what should i do ? I guess i have to spend some shit on a new battery. But apart from that, iwanted to know about performance. how to get a beter performance?

I have heard of solutions like getting an sdd or increasing ram, but am broke af and might not afford a 1tb ssd (yes i do need that much amount of memory, my system is currently at 650 something gb) and about ram i have heard it doesn't offer much improvements. is that true?What should i do?

One of our dev team had the task to do a bulk operation for thousands of objects.
So time passes by and they implemented it. But in acceptance testing they found out that this operation takes 4 minutes for 50 objects. This is not what we call high performant when we talk about 20000 objects per bulk operation 🤔

Well, their PO asked them to solve that performance issue. And guess what, they decided on their own that the issue can be solved to reduce the bulk to 20 items so that it only takes 2 mins to run!

Really guys, is that the best you can come up with?! 😲🤬

I hate eclipse due to the performance issue... switching perspectives, just everything seems too slow.

Love sublime and it’s speed, and simplicity, as well as vim ..of eclipse had the editor of vim... with key bindings of vim... speed of sublime or vim...but the ilitellisense of eclipse or visual studio ..and the ability to properly change the theme/color scheme of the entire environment without issues of contrast with certain plugs in...

I think eclipse would actually be great if someone did that... or same with Visual studio ...

Is it a good approach to use MariaDB in one Server and MongoDB in another one to store various client's data?
The reason I need MongoDB is because the client has to create custom Maintenance Checklist (which mean he has to create rows and columns), and then submit these data based on specific period. And I am finding hard time how to design this on MariaDB, even with dynamic columns since it might bring performance issue.

I want to resign my job as fresher with 5months experience. Because the work culture is toxic, I will not be assigned tasks properly and then I have to sit idle for hours waiting for review. I feel so sick. They fired one guy who joined 4months back stating performance issue when they didnt manage him properly.

We had an issue where a query to a db replica set was returning duplicates randomly when paging. Aka each HTTP call for next N results was hitting different dbs with same/copy data.

No one could figure out why... I look at the query and ask where's the ORDER BY ID?

These guys were interviewing ppl last week and saying how even they could solve algo questions they were asking candidates.

And so to explain the problem, I'm like "tell me what's the difference between a list and a sorted list?"

#why algo questions suck at predicting job performance

I installed VS Code a few days ago and I'm really struggling to see all of these apparent massive benefits over Atom.

I have a pretty decently specced machine so performance is never an issue.

Is there something else I'm missing?

So, I just (few hours ago)made a new variable that's either brilliant or innately flawed... not sure yet. It's an oddly unique var...

__bs__

So far I only made it in python and windows env (i script like the methodology of css).

I bet you're wondering how I've defined __bs__ and the practicality of it.
__bs__ is derived from a calculated level of bullshit that annoys me to tolerate, maintain, etc. as well as things that tend to throw nonsensical errors, py crap like changing my strings to ints at seemingly random times/events/cosmic alignments/etc or other things that have a history of pulling some bs, for known or unknown reasons.

How/why did this come about now?

Well I was updating some symlinks and scripts(ps1 and bat) cuz my hdd is so close to death I'm wondering if hdd ghosts exist as it's somehow still working (even ostream could tell it should be dead, by the sound alone).

A nonsense bug with powershell allowing itself to start/run custom ps1scripts with the originating command coming from a specific batch script, which worked fine before and nothing directly connected to it has changed.

I got annoyed so took an ironic break from it to work on python crap. Python has an innately high level of bs so i did need to add some extra calculations when defining if a py script or function is actually __bs__ or just py.

The current flavour of py bs was the datetime* module... making all of my scripts using datetime have matching import statements to avoid more bs.

I've kept a log of general bs per project/use case. It's more like a warning list... like when ive spent hours debugging something by it's traceback, meticulous... to eventually find out it had absolutely nothing to do with the exception listed. Also logged aliases i created, things that break or go boom if used in certain ways, packages that ive edited, etc.

The issue with my previous logging is that it's a log... id need to read it before doing anything, no matter how quick/simple it should be, or im bound to get annoyed with... bs.

So far i have it set to alert if __bs__ is above a certain int when i open something to edit. I can also check __bs__ fot what's causing the bs. I plan to turn it into a warning and recording system for how much bs i deal with and have historical data of personal performance vs bs tolerance. There's a few other applications i think ill want to use it for, assume it's not bs itself.

*in case you prefer sanity and haven't dealt with py and datetime enough, here's the jist:
If you were to search any major forum like StackOverflow for datetime use in py, youd find things like datetime.datetime.now() and datetime.now() both used, to get the same returned value. You'll also find tons of posts for help and trying to report 'bugs', way more than average. This is because the datetime package has a name conflict... with itself. It may have been a bug several years ago, but it beeb explicitly defined as intentional since.

We ended up finding ourselves with a bunch of tables that have mostly the same columns, but differ by a few. Every time we consume a REST API, we store the `access_token`s and expiration dates and the other OAuth data. However, each provider has slightly different requirements. For example, we store email addresses for email api's, other providers require us to store some additional information, etc. etc.. I'm tempted by the flexibility and lack of schema brought by document databases, but not enough to use one since they're generally slower and we already have everything in SQL. So I got the idea of using JSON columns to alleviate this issue: have a single table for all REST integrations (be it outlook or facebook), and then store the unique integration data inside of this JSON column for "additional data". This data is mostly just read, not filtered by (but ocasionally so). Has anyone had experience with this? How's the performance of JSON fields? Is this a good practice or will it get harder with more integrations?

Going crazy with GC logs, HeapDump and ThreadDump😶Application performance issue😬

Having this stress at work especially when they monitor your performance during the WFH . Not doing rocket science or stuffs. but angular front end dev.
api dependency was delayed.
Stuck at some bugs which I think user can never reproduce but a tester did.
All of them is busy with their own ML stuffs and impediments.
Having issues with staying home and work. I dont know this is just me or someone else having the same issue. I am just trying to share. Anything you wanna add?

I want to keep 1 year of daily indexes but for the ones older than 30 days, unloaded from memory. But accessible when needed.

So like say there's a performance issue today and I want to compare all the activity against 2 months ago. I can open the old index and search it.

Can you do that, does closing remove it from memory? Otherwise how would you do that?

VSCode. I used to be a WebStorm guy, but at one point I found out that I could do like 85% of the stuff in VSCode, and switched over. Things I still kinda miss from the JetBrains ecosystem:
- the elaborate refactoring
- the built-in navigation across the file and the project
- the really clever expand select and go to open/closing bracket (VSCode is kinda getting there, but for expand select it honours camel case words and that can't be turned off, it's weird with HTML files with inlined JS or CSS; for bracket jumping it must rely on an extension)
- the way that everything within the UI is predictable and navigable with keyboard only (tried opening a dropdown in VSCode without having a specific keybinding for that specific dropdown? In WebStorm it was Alt+Up/Alt+Down for any dropdown that has focus IIRC)
- the visual way of changing a colour theme (in VSCode you have to guess what is what before modifying a value; by the way this is an idea for an extension that I might research)

What I like about VSCode:
- the speed (although it can get slow with large files; on the other hand JetBrains IDEs are not that slow except for the startup, given that you're not working on a potato, but here we are)
- its extensibility and very active extension development (and the fact that it's rather easy to write your own extensions, although I haven't benefited from that very much)
- the ease of syncing settings (the Settings Sync extension and now the built-in mechanism introduced I think earlier this month)
- it's free (so I don't have to pay for it myself or nag to my employer to issue me a license)

I've tried Sublime and it's hands down the fastest thing I've seen (it can open a 100 MB text file on the shittiest computer you can find and edit it efficiently), the problem is that it's not so rich in extensions. I've tried vim, nano and whatnot, but I'm far from that, just not my cup of tea. I'm okay for the occasional file edit while SSHd somewhere, but that's all.

In an ideal world we'd have something like Sublime's performance with VSCode's ecosystem and JetBrains', well, brains...