If you don't think AI will include sponsors/ads/etc once someone comes out on top, well, I might have a bridge to sell you.
Seriously though, I'm not sure why Google evolving in this manner precludes them from having a profitable business model. Right now we're subsidizing the costs (probably just a bit) and having ongoing subscription revenue they can increase as needed (particularly in the "google won the race" scenario) will be key before they even have to consider layering advertising on top.
Every 5 years on average since the late 90s the industry has doubled in size. Add in natural attrition (and the other things you mentioned, ageism, management or other tech adjecent careers, etc.), and even accounting for a modest number of "second career devs" starting later in life rather than out of college, you still have an industry that skews younger simply by virtue of overall growth patterns.
I think that is significantly overlooked when people ask "where are the 50+ engineers?".
While there was a lot of FUD in the media, there were also a lot of scenarios that were actually possible but were averted due to a LOT of work and attention ahead of time. It should be looked at, IMO, as a success of communication, warnings, and a lot of effort that nothing of major significance happened.
Unless you're forced into using certain tool (work, etc), start by standardizing on a single tool. That's one reason a lot of people like Obsidian, but there are plenty of similar tools, or you can just write markdown in your editor of choice. Then set of some sort of sync so you have it everywhere you are (mobile can be a bit tricky for some set-ups) and commit to using that method as much as possible for your notes.
You may want to do as described and link to Slack messages (etc), but just remember any external link should be treated as ephemeral. You may not have access to the Slack anymore, for example. That may mean you don't need that note either, or it may mean you lost access to a node on your knowledge graph, you have to determine whether that matters.
By starting now, at least everything going forward is captured in a way you can both own and utilize it. Then it may be a bit of a pain and some manual work to get existing notes into your tool of choice, but you can determine what needs to be in there from other tools as you go forward.
Bit sad that the DevTools Accessibility Inspector was one of the "superfluous" items, at least without a "if you're not a dev" type of disclaimer. If you do any web development, seems like a worthwhile item and I'm happy it is surfaced by default to help promote it's use.
Obviously, no issues with non-devs who would never use it disabling it.
This is a great reminder that I need to re-incorporate exercise into my routines, thanks! It fell out a little while back, and it has a very positive effect overall.
Resist the urge to over-complicate things. With ADHD, it's really easy to hyperfocus and end up building a "beautiful" system that doesn't work at all for you. Then you give up and start all over. So instead, pick small things that you can incorporate into routines, which are a saving grace especially with ADHD - just include enough space for a bit of flexibility so it doesn't get stale/boring.
For instance, I have a morning routine which ensures I'm "presentable"/etc. When I start work I immediately create the day's note, go to the previous day and review, copy over any ongoing tasks, etc. My day note is the same thing every day: Things I did, Things I need to do, Meeting notes (important meeting notes get extracted to their own file), Random notes. Then setting in to work. Evenings are bit more flexible and the weekends tend to be the wild west, bit of a reset so I don't feel "trapped" in a cycle, etc.
I do struggle with weekly/monthly or longer intermittent routines. Even stuff like doing bills (automated as much as possible), re-ordering prescriptions, etc. So it's always a process.
Last thing so as not to go too long - not everyone runs into this, but in case you've gotten down on yourself at times and now realize it might be ADHD, give your self a break / forgive yourself. Same thing going forward. Not an excuse, not continuing to seek improvement, but realizing that when you stumble, there is a reason and it may not be something you can actually control. Reflect on what you could do to prevent it in the future, but do it without self-blame or criticism. Be kind to yourself, in other words.
FWIW, I do aim for inbox-zero for email, and similar for chat apps (Slack/Teams). Otherwise it piles up and gets overwhelming. I'm referring more to things like - "only the exact thing you're currently working on open" part. I agree systems are needed. For me it's Obsidian for notes, inbox zero, and OneTab extension to allow me to remove tabs without fear of "losing" them completely. I've learned that it's also a trap to over-complicate my system, even something like Todoist which is fairly minimal was semi-problematic, although I may come back to it - just using manual TODO checklists in Obsidian with a small table that pulls them all into a single dashboard file for reference.
The author found something that works for them, but for some folks who have working memory issues (i.e. ADHD), using visual cues as reminders is one of the top tips in ways to address the issue. This can seem messy to some, but for those that need it, it is a lifeline. As a contrast to the author, if I put something in a drawer, it might be months before I remember it, even if it was something that absolutely needed to be dealt with (and yes, there will often be consequences of having not done the thing, and this has to be balanced against leaving everything out which isn't good either). Electronically, if I close Slack/Teams, I might go hours before remembering to open it and check in - maybe great for focus, not so great for team work.
I've found that for me, spreading things out and having visual cues allows my brain to relax and focus on the task at hand, because I know I don't have to use a memory slot to remember to do something that I don't have a visual cue for, because every so often I see that cue and know it isn't going anywhere until I have time to deal with it. Almost the exact opposite of the anxiety the author describes. (And before it's suggested, yes, I also take notes and put important tasks there, but it isn't as helpful for my brain to let something go compared to having a visual cue.)
> Claude is an LLM. It can't keep slaves or torture people.
Yet... I would push back and argue that with advances in parallel with robotics and autonomous vehicles, both of those things are distinct near future possibilities. And even without the physical capability, the capacity to blackmail has already been seen, and could be used as a form of coercion/slavery. This is one of the arguable scenarios for how an AI can enlist humans to do work they may not ordinarily want to do to enhance AI beyond human control (again, near future speculation).
And we know torture does not have to be physical to be effective.
I do think the way we currently interact probably does not enable these kinds of behaviors, but as we allow more and more agentic and autonomous interactions, it likely would be good to consider the ramifications and whether (or not) safeguards are needed.
Note: I'm not claiming they have not considered these kinds of thing either or that they are taking them for granted, I do not know, I hope so!
I'd say what you call bloated is in many cases basic functionality that I don't have to go looking for some third party package to fill. There is something to be said for having a straightforward and built-in way to do things, which leads to consistency between Angular projects and makes them easier to understand and onboard to.
IMO, it is only as complicated or simple as you want to make it these days, and claiming otherwise likely is due to focusing on legacy aspects rather than the current state of the framework.
FWIW, I'm not arguing that it's the "best" or that everyone should use it. Or that it doesn't still have flaws. Just that it is still firmly in the top set of 3-5 frameworks that are viable for making complex web apps and it shouldn't be dismissed out of hand.
I know you are saying you do work mainly in Angular, but for others reading this, I don't think this is giving modern Angular the credit it deserves. Maybe that was the case in the late 20-teens, but the Angular team has been killing it lately, IMO. There is a negative perception due to the echo chamber that is social media but meanwhile, Angular "just works" for enterprise and startups who want to scale alike.
I think people who are burned on on decision fatigue with things like React should give Angular another try, might be pleasantly surprised how capable it is out of the box, and no longer as painful to press against the edges.
Sometimes it is nice to have a separate application for notes compared to the editor being used for code. It means they can be customized for their individual purposes. Sometimes there are minor inconveniences (I miss multi-select/change in Obsidian sometimes), but even when I used an editor for my MD notes, I found myself using SublimeText for that while I used VSCode or IntelliJ for coding. Just a 1 of 1 experience, but as mentioned elsewhere, there is a large adoption of note taking apps separate from code editors, and a few of them use markdown as the underlying file type which I require for anything I use for portability.
FWIW re: performance, I love Obsidian, but performance is it's one main downside for me. I could care less about the real-time collaboration (they are my notes, not for team consumption, I'll share a file somewhere else for that) or self-hosting (sync so my notes exist wherever I am is more important to me than hosting them anywhere, again, my notes are private on purpose; obviously that isn't the case for everyone).
Anyways, just a counter-point to the commenter you were replying to.
My understanding, the SVGs were imported directly and embedded as code, not as a `src` for an img tag. This is very common, it's a subjectively better (albeit with good security practices) way to render SVGs as it provides the ability to adjust and style them via CSS as they are now just another element in the HTML DOM. It should only be done with "trusted" SVGs however!
As for CORS, they were uploading the SVGs to an account of their own, but then using the vulnerabilities to pivot to other accounts.
If I can run my own code but in your context, I can pull in malicious scripts.
With those (all these are "possible" but not always, as usual, it depends, and random off the top of my head):
- I can redirect you to sites I control where I may be able to capture your login credentials.
- May be able to prompt and get you to download malware or virus payloads and run them locally.
- Can deface the site you are on, either leading to reputational harm for that brand, or leading you to think you're doing one thing when you're actually doing another.
- I may be able to exfiltrate your cookies and auth tokens for that site and potentially act as you.
- I might be able to pivot to other connected sites that use that site's authentication.
- I can prompt, as the site, for escalated access, and you may grant it because you trust that site, thereby potentially gaining access to your machine (it's not that the browsers fully restrict local access, they just require permission).
- Other social engineering attacks, trying to trick you into doing something that grants me more access, information, etc.
Seriously though, I'm not sure why Google evolving in this manner precludes them from having a profitable business model. Right now we're subsidizing the costs (probably just a bit) and having ongoing subscription revenue they can increase as needed (particularly in the "google won the race" scenario) will be key before they even have to consider layering advertising on top.