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-...
> 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.
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?
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.
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...
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 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).
Indeed, and pragmatism should be applied, but I mean in the context of not being rushed. I don't mind my team watching YouTube/browsing the web during work if things are going well but I wouldn't accept it if it's done after submission of suboptimal code. If there's time to watch YT, there's time to improve your code (unless it's clearly too much of a refactor).
I think people who recognise this have generally been developing from the days where computing resources were scarce (or on mediums now where they need to be efficient). It was a necessecity to implement efficient techniques instead of a nice to have. Nowadays those restrictions have been lifted for the most part.
In this day of "Agile" development, as long as something's working during UAT, that's all that's needed for sales and consumers.
Webdev, IME, is an example where the ecosystem has facilitated bloated websites. I've worked with developers who throw any library they can just for basic things because they don't have a need to try to optimise. The meme of using jQuery for everything when it came out has just been replaced by other frameworks. I find it often depends on developers who really want to work on something and take pride in it vs those who just need something on their CV or got hired by following a few tutorials on the web but not understanding what they wrote (which, to me, signifies a hiring problem in the company). During code reviews, I encourage leads to keep calling up hacky code to a point where the developer will just start writing it properly the first time round. As developers, I feel we should be aware of not creating selfish software which hogs memory from other software or requires huge data downloads for mobile users (whenever doable). Possibly a naive ideal but if it's a byproduct of developing fast software for my end users, I think that's a win-win.
Depending on your situation, the other answers in this thread may help. Assuming they're not viable for you, you could try reframing the situation. You now have something to look forward to on your off time that can be used to help during difficult times at work. Also, working on a project that you like all the time could maybe make it less appealing over time, similar to over-listening to a song. Maybe you haven't realised it but the immersion you have could be because you have breaks in between sessions for work.
Not just megacorps, I've seen long unproductive meetings in startups which means a larger percent of the workforce out of action for the duration. Often I find managers who insist on these types of meetings, frequently, are the same ones that don't really seem to be providing much value generally outside of meetings.
Whiteboard - For me, tangible writing helps with creativity and thought processing and a whiteboard saves on paper if it's not going to be a permanent thing (and even if it is, a simple photo of the board for retention).
Google Keep for quick notes on the go with a permanent pinned tabbed in my browser for quick access
Trello for day to day development management but not as detailed as I would in my work, simply as I don't need it to be. Speed is an advantage for solo projects and small teams so adding unneccessary processes reduces that advantage IME.
Specialised comments within Visual Studio to allow me to write comments and easily find them again without disrupting my flow (I believe IntelliJ and other IDE's may have analogous features) https://keyboardp.com/post/40190774577/using-task-list-token...
Unless Kiwi browser supports Google Chrome user profiles, the main advantange of FF over Chrome on Android, for me, is the ability to share webpages seamlessly.