I think soon, we will be adding “Skip Claude” in the same vein as “Skip Intro” to this list.
However, this is personal, but I stopped caring as long as the content is good, the animations can do justice in explanation and I get to learn or get what I want from them.
I learned this the hard way. I have been training a bunch of 5-10 years experience tech-leads, architects, and what not. But on the job, I realized quite a lot cannot switch context and subject at all.
I've found people who have spent decades on one topic in a very specific vertical. It is amazing how they know EVERYTHING in that and I can listen with my jaws dropped to the floor for hours. Then I will wake up, with that spine-chilling shake all over my body on how patient and dedicated one has to be to be on that straight line their entire life.
LOL! My bosses used to tell me that I need to learn to be more `rude` and not just do what others says because I can. I have learnt a lot and one of the biggest is to say NO, in big Uppercase—I can do anything for work but I won’t do that, NO, I won’t do that.
Sometime, I still do and I like the fun and thrill of locking in a hotel room after a meeting and coming out in lot less days these days (pppppsssstt, because of AI) and get into the next meeting showing off what can be done that was discussed 48 hours ago.
You don't do these things because they benefit your boss. (They might happen to, but that's not the point.)
You do them because they benefit you.
Not going to benefit you? There's lots of ways to say no to a back-channel request. Not a back-channel request? Then I guess it's not someone else's job!
Easier said than done. Saying no is not so easy. There's a bit of a weird dynamic that if you could do something that others need help with, saying no can be considered rude, but saying (even if lying) that you don't know how to do it is generally accepted. Usually a boss (or even a colleague) backing in saying no helps a lot.
Also the helping can cause escalation of "demand". First you help with something quick and easy for you, but soon you find "owning" more and more of the task.
It's not dissimilar from the entitled people in open source project bug trackers.
Personally, you lost me at `.capsule`. I assume this is your format? Now, what happenss when you are not around or I don't have access to you when it is needed most?
Not defending ant entity (Apple here) but you need to decide which is it—delete your account when done or saved forever. Everyone yells privacy, “Account Delete” must but when it happens, you cry all over.
Anyways, in a different take, I always have my own copy of things that I have and own. I tried to stop our family’s Apple One subscription a few years back as we were rarely using it. This was the time my daughter was all about Spotify, its “smart algorithm” and such. So, I decided to move our family music to Spotify so I can have one place to manage. She stayed, but Spotify isn’t for me—I’m getting older, so I know what I want and stick to my lane.
Came back to Apple Music (via ONE), the quality is way better and I just let it rescan my local library and we are happy again with the library + few that I missed in my collections.
There is no "Apple music account". You subscribe and unsubscribe using your main, only, icloud account, that is tied to your payment info, keychain, icloud mail and everything.
> you need to decide which is it—delete your account when done or saved forever. Everyone yells privacy, “Account Delete” must but when it happens, you cry all over.
Requesting account deletion should delete the associated data, but a paid subscription lapsing doesn't need to.
It is weird that quite a few developers comes up with advices where they seem to come from a world where they work alone, have not work with enough people, or with enough projects.
In this case, a `.gitignore_global` takes care of the usual suspects that he mentioned `.DS_Store files, IDE config, compressed files, etc.`. Even if something goes wrong, it is usually caught during the initial scaffold before critical files goes in.
If one is working with new, young, rookie developers, give them the typical lesson on the global gitignore, local, config, and to have dotfiles, etc. Give yours for inspiration or something to start with.
Edit: I know that mine is not the best of the dotfiles on the internet but this has helped me switch multiple devices, multiple identities (work, projects, personal, etc) easily. I recently cleaned it up and added automation, test, etc with Claude Code. https://github.com/brajeshwar/dot
> It is weird that quite a few developers comes up with advices where they seem to come from a world where they work alone, have not work with enough people, or with enough projects.
I wish there was a culture in the team I'm in now to share each others dotfiles (which I feel would lead into sharing so much more including tools, processors, etc), especially since I fall into that group of the new, younger rookie. I appear to work with people who have a lot of experience and knowledge and the atmosphere is seemingly otherwise not competitive (non profit organisation). Is this common? Is it going to be hard to find a team like that?
My daughter plays games like crazy. She plays a lot of them, started with MineCraft when she was young. I think they are all fantasy games.
She has defined a life she wants to live and is scarily detailed. It is sort of an NPC lifestyle. I believe she is inspired by the games she play.
She might change but for now she seems have a clean outline of how things will be, work, home, and everything else like a very finite number of friends, the things to own, no brand logos (or should be really muted/subtle), etc.
I'm curious how did you go about accessing the data source for projects liek these? I mean, I have seen quite a lot of interesting builds (even if they are AI-assisted) but I love the results.
Wikipedia as a data source is open to use for everyone which makes this project even possible. Without Wikipedia, I would have to rely on Ai generated results which is not optimal.
I find it easier to try out the common tools here first and then decide if you need something bigger, heavier to move to a VPS or your own server.
reply