It also doubles as documentation that’s forced to stay up to date. Code has a way of becoming hard to follow especially when edge cases and performance enhancements are added.
Alfred can either replace spotlite or run along side it. I’ve found it much faster and easier to use. You can customize it pretty well. (Just don’t download the Mac App Store version as it’s multiple versions behind)
There’s a ton of windows managers out there that help you setup hot keys or modify windows to work how you want. Mac overall is much better with native software not doing its own thing than windows so changes tend to be pretty consistent. I’m using MOOM because it’s on the app store and lets me hotkey all my windows into specific sizes but there’s plenty of other stuff out there depending on what you want to do.
I think the problem here is that there are very few places where there is any time between pressing feature demands. This always seemed to me what the agile guys were saying. The approach was all centered around the idea that things would always be changing and pressing. The only way to combat that is to put constant refactoring into the day to day so that your codebase can remain coherent and productive to work on.
The bonus of doing things like this is that if you are constantly changing your code then it becomes battle hardened to accept change. This gives you better ability to keep up with the changing demands of both customers and technology.
It takes a bit of time. You’d want to do it one by one. I’ve done it the other way (mono repo code to library) and it’s worth the time to keep the history around where you are working. I just did a google search. First one that comes up tonight is this article: https://medium.com/@ayushya/move-directory-from-one-reposito...
Some of the best engineers I’ve ever worked were just “going with the flow”. They certainly brought tons to the table. Some people are just quiet and don’t like conflict. If you ask them what they think plus give them a calm environment, time and support you can find yourself looking at some very elegant easy to maintain systems.
I think it’s more about the centerpiece being subjects rather than people. I read Reddit threads all the time and comments there are front and center. There’s plenty terrible subs and people but they are easy to ignore and not the norm with what I look at.
It’s kind of fascinating to me that things have ended up like this. There was a period where Facebook was incredibly bland because people were using their real names. At some point that boundary got crossed and now most of what I see when I look at it is excoworkers who would have never gone on about politics around the workplace trying to get their message across. The rest of the people I followed who posted interesting moments about their lives have stopped posting altogether.
I’m surprised Reddit is even considered social media. The anonymity of the users and focus on subjects over people make it a very different experience. With Facebook and instagram you have a limited pool of people that interest each other and if they stop posting they have to figure out what to show you. That’s… really hard, especially if you signed up with these people in mind.
With Reddit meanwhile you can easily select the subjects you are interested in and there’s a bottomless pit of people who can post and comment on that. While it being mostly text based will probably limit how big it can get compared to something like TikTok I suspect there’s a better slow and steady business model with less churn.
I also really like that they offer a monthly sub at a fair price that removes the ad problem. I really wish more companies would take this sort of approach.
Those were so awesome because they explained the whole system. The core graphics one was an absolute lifesaver when I started working with iOS. Apples UI a frameworks seemed way more complex than anything I’d ever worked with before but once I understood the layers they started to click. I don’t know what I would have done with a bunch of class guides with patchy comments.
I really wish apple would spend more time on their tooling. A lot of the new features like async/await and SwiftUI have way less visibility than what came before. A lot of this stuff makes the code compact and much easier to read but when things go south trying to use the inspectors they have often doesn’t get you very far.
They do start to care when it stops working or it takes forever to change due to it being a mess. This is the natural state most projects end up at unless the devs are putting in a ton of extra effort to keep it clean, organized and maintained. Devs that are thinking about keeping things beautiful, succinct and performant are much more likely to do that.
My Observer bias of late has been about open or nearly open feedback loops. People don’t adjust their strategies when the consequences come due later. I’ve been on a number of projects and seen a few more where management keeps turning screws to get stuff faster and then goes pikachu face when the whole thing grinds to a halt. Few if any of them see themselves as the agents of chaos in this situation. It’s not their fault, it’s someone else’s. And even if you can document it, it doesn’t sink in. Because that was something they did years ago and we don’t think about old things.
