I realised I have quite a few random scripts I use for myself or to improve my usual workflow. Recently decided to start blogging again and figured some of them might make interesting reading for others. Lately:
I also wanted to use ChatGPT over my own files and documents. Whilst my personal system is a bit more complex, created an end-to-end tutorial of my learnings to get started with using your own docs: https://www.reaminated.com/run-chatgpt-style-questions-over-...
Ayurveda posited a form of gut-brain axis thousands of years ago (and is a core basis for its dietary aspects), interesting to see more scientific research delving into the details.
Not sure what your point is here. I'm suggesting that dietary aspects were designed around the aspect of a gut-brain axis and praising that more research is going into the details. Similar to how we're seeing more research in the field of meditation and its impact on brain structure.
Source on Ayurveda posits that palm reading is legitimate medicine?
Apologies. Presumably those thousands of clinics etc in the search results "posit that palm reading is legitimate medicine". I had to guess what your question meant exactly - as is, it's not grammatical english, and is ambiguous in at least two ways. I should've asked you to clarify instead, or just not tried to answer.
> Presumably those thousands of clinics etc in the search results "posit that palm reading is legitimate medicine"
Not really, they're more astrology based, not medicine, and no one is claiming astrology is factual in this thread. Also, they're clinics, not a source of any kind which is what was asked for.
I think this is partly why Rubber Duck Debugging[1] can sometimes work, especially if you're vocalising the steps. I've often started typing a question on Stackoverflow when suddenly I solved the issue just by the act of verbalising the question as I type.
I've found this to also help when I'm doing any sort of creative work or brainstorming, simply talking and explaining as if I'm presenting to an audience helps me generate ideas. Never spoken out loud to myself in public though...
the shift from a asynchronous communications (email) to real-time chat (slack/teams) may have led to a significant reduction in "thinking things through"
Writing an email or a SO question has a pretty significant upfront investment and requires clearer articulation, whereas real-time chat seems to lead to shallow enquiry.
In other words with real-time chat, the recipient has become the rubber duck.
Absolutely. I don't personally use a rubber duck when alone but we call it that in the team when you just wave someone over to your desk to talk something over (and now virtually in a quick call).
I personally have always liked writing down my "conclusions" so far into an evolving comment on a defect/bug ticket, which I only actually submit at the end when I've found the real issue. In the end you have a nice explanation of what exactly and why it went wrong and it helps with the actual debugging/thinking it through. And it also helps with the inevitable comments/questions in the PR when people wonder why the hell you are making the change you're making and you have something refer back to.
Quick feedback, the video on the landing page doesn't have a full screen button, or double click support, so the text can't be read (I'm using Firefox on desktop). It's pretty self explanatory so the text isn't super important but I think it takes away from the video unnecessarily.
I find being transparent with my team makes it a lot easier. There are internal deadlines and external deadlines. Former are internal ones which have no real consequence if missed and just keep a development rhythm (e.g. weekly iteration, monthly release, quarterly roadmap update catchup etc...).
The other type comes from third parties, generally, such as clients or the board. Once you separate these two types of deadlines, I find my engineers more understanding about having to meet external ones whereas blurring internal and external into one "deadline" simply causes people to either burnout or lose faith in management because everything is marked as urgent.
I've found most deadlines I've worked with to be internal. The only exceptions to that however was legislation dates; Cookie walls and GDPR, new laws for stock trading on an European level (forgot the name), things like that. These are things for which your company can be fined heavily for. Other deadlines are likely to be of the "we'll start earning money later" variety.
Those are BS as well. No one is going to fine company on day 1 of a new law. GDPR was effective 25 may 2018 but companies still had half of a year to implement it.
Basically if you prove you are working on it I bet they will let you off the hook.
I work on a lot of features lately handed down from the CEO of our client. And he places deadlines so unrealistic his own team oftentimes doesn't get us the details until a couple of days before the deadline. For work that takes weeks to do.
Stuff is constantly pushed back. The India launch so far has been pushed back 9 months. A new product launch in the USA was pushed back 3 weeks - he initially said they were launching January 1st, when they get 2 weeks off for Christmas and no one works on new years day. Lol.
It sounds like management at your company isn't doing a good job pushing back on these requests or insulating the dev team from this unreasonable client?
But you work for your CEO, not your client's CEO. Even Steve Jobs called Larry Page, not a random engineer, when he didn't like the Google icon on the iPhone.
I don't quite agree here, developers need to have an idea of what they're working to so they can manage their own implementation time. If you don't make developers aware, you put too much control in the manager's hand which isn't a good thing here (unless you're referring to a developer lead but even then, individual developers should have an idea of when they need to complete by).
