oscarcp

I was about to that myself this weekend, you just saved me few hours, I'll start using it right away :)

You're completely right but I am "flipping the tortilla" on this one and thinking, it's great that they're just spitballing stuff, it's bound to eventually find something truly interesting and/or useful! (in n+1 time but I don't mind!)

Completely agree with the 5 minute rule, as I mentioned in my comment, it's one of the steps (for me at least it was)

I'm quite familiar with that, unfortunately, and for me it didn't only span days, I spent months unable to be productive (you can guess what happened) and the last 3 years struggling to keep up (as a reference, I was one of those so-called 10x performers).

Of course each one of us is a different universe, but let me tell you what helped me (I repeat, this is a personal experience, I'm not a doctor):

* First, do not get anxious about it, otherwise you will feed it and it will amplify.

* Second, force yourself to 5-10 minute work, and I mean force yourself, pick a task, any task, push your brain until you are able to do 5 minutes of work, if you are able it's a good sign

* Third, question your physical health, are you ok? Do you have enough vitamins, etc? A blood check doesn't do any harm. I've found iron deficiency is a big part of not being able to work.

* Fourth, question your mental health, your brain is the most idiotic organ ever, it doesn't know when it's ok or not, do you feel anxiety, stress, impostor syndrome, is there something missing in your life that was previously there? Repeat this until you get clear answers.

* Fifth, process those answers, really process them, they will give you clarity that will lift the mist.

* Sixth, check with a psycologist, my recommendation is that it's specialized in cognitive behavioural therapy.

All of this being said, after points 1-5 I was still struggling, on and off (mostly off) for a while until I did point 6 and this helped me move forward slowly with a lot of "homework". I can't tell you exactly what my issue is because I have many and they're quite intertwined, let's just say that I was brought back from the brink (at the time I did number 6 I started already with anxiety and panic attacks)

You make quite the point here. That is the advantage I see for DDD; you have dependency on service that may change, DDD will make your life easier when switching, otherwise there will be weeks of rewriting code. And what happens during transition times (thinking about CRM for example) where you have to keep connected to both systems?.

This said, in my situation it's like trying to kill flies with a muon cannon (fyi. this gun is fictional and it's exaggerated to drive the point), it's cool'n's*it but the same could have been done with a newspaper or your hand. To maintain the muon cannon you need the entire Fermilab team, your hand... well, it's your hand.

Apologies for the exaggeration, can't avoid it :D

> Your story sounds like they implemented a "technical DDD top-level architecture" (TM), whatever that may be. (I'd assume layers of abstractions coupled with logic spread all over the place, without any added benefit.)

Exactly :)

Python, FastAPI... so you can imagine how something as simple as a CRUD becomes quickly impossible to manage as soon as you ignore everything and start creating repositories, queries, use cases, etc. for a single endpoint.

I agree with you that a minimal implementation should handle it but... someone had wet dreams with DDD and everything has to be DDD now :)

At the moment, there's no way out, plannign stipulates that all our microservices must be rewritten to accomodate this super abstract DDD design (and youy're right, it was an engineer who created our current layout)

We use DDD at the current company I work in and to be honest, I detest it so much that sometimes it makes me wonder if I even want to continue in the programming space (been at it for 20 years).

Don't get me wrong, DDD has meaning and purpose, but some companies are applying it as a badge to be obtained instead of pondering the question, do you really need to rewrite everything following DDD?

In our case, simple CRUD APIs that in "regular programming" might take a couple 200 line files have turned into unmanageable nightmares in DDD that take you at least a couple of days of really intensive investigation to understand, because it have been divided in more that 25 files that hold 3 or 4 lines of code at most, with so many abstraction layers that it's impossible for the best of us to follow in one go.

Now, you could make the argument "You Are Doing It Wrong(tm)" but since I'm just a drone in this specific scheme and there's no wiggle room for anything (the team is quite inflexible on this) I have to follow it to the letter.

Just giving my two cents, again, not depreciating DDD, it has its purpose but in my opinion, it's for very specific projects.

One detail, not all phones have the light sensor in the top bezel, some phones like OnePlus 7 Pro have it integrated inside the fingerprint scanner, so depending on your phone the light sensor might be located somewhere else.

As far as I know the default behaviour of Google Maps is to switch light/dark mode depending on the feedback from the light sensor next to the front camera, so basically as soon as it detects a lack of light, it will switch to dark mode.

It does, when you try to access a blocked URL it will redirect you to a local webservice that will tell you that You! Shall! Not! Pass! :D

Step 1: Keep your knowledge as sharp as the sharpest knife. Knowledge is the ultimate currency.

Step 2: Research people's attitude during that time (every recession creates a change in behaviour and personality) and find a personality trait that will match it so you can gain their trust or affection (not in the partner sense), especially higher ups that can give you employment or any other sort of resource (recession is not a time to be thinking of money as the only resource).

Step 3: Meet people, force yourself to do it and apply those traits. Don't become an asshole in the process.

Step 4: Repeat with other resources that may be handy during that specific recession. Diversify.