I do see your point, and I agree that covers most cases, but can it really be a definition if it doesn't cover all cases? Are just talking about a distinction between "edge" in an architecture vs "edge computing?"
My takeaway from this is that a lot of people disagree on what "edge" is. IMO, "edge" is the furthest resource that you have some computational level of control over. Could be a data center, could be a phone, could be an IoT device, could be a missile.
EDIT: I think I'm realizing people will disagree with me because I have a different perspective. For my use cases, my data comes from sensors on the edge, and so for me, I want my edge computing to be as close to those sensors as possible.
Officially, my employer has moved on to three common "in office" work days per week (T-Th). Unofficially, that's a goal and people still often work from home during those days. But it's nice to at least have a compromise. It isn't the one I'd prefer (1 or 2 days only), but it acknowledges that employees want to keep it, and similarly employees acknowledge that for our particular industry we do sometimes need in-office or in-lab time. It also allows employees to push back on any in-office meetings on non-common days per official policy.
Can someone that understands ML better than I tell me if there is a point where the AI can indefinitely train on data generated by other AI? If AI is trained on human development work product and then it eliminates human developers, will the capabilities of the AI be stuck indefinitely at the level of the software from which the models were trained? Not sure if I'm making sense, but the crux of my question is: can AI effectively generate their own training data sets? If not, then I don't see how it could replace an industry.
To that parent's point, < 1% has gone to charities which means the foundation is just spending money on the people that work in and own the foundation. I wouldn't need to get paid directly if I had a foundation that paid for everything I need or want.
Wife and I use Bitwarden. My master password is in hers and hers is stored in mine. I once toyed with the idea of building a "dead man's switch"-type service that requires clicking a confirmation button of some sort at a regular interval and which would then send any info you want in the form of emails and/or a physical courier. I looked around and saw a few available so I dropped it. But I haven't subscribed to such a service myself.
This feels oddly specific. I'm not sure why you can't engage on Twitter and still not be "lacking in real life." Who even gets to define "real life?" And while I'm sure some people spend 20-30 hours per week on Twitter I'm guessing it's such a small percentage of the world that it might as well be statistically insignificant.
> > Should I tell my boss and/or team?
> No, they will stab you in the back, no matter how much you think they won't.
I disagree that this is universally true. I have had at least 2 bosses that I know would help deal with burnout because 1 of them helped me and the other I have seen help others in this same situation. A good boss cares about their employee's health and wants to keep good workers. I agree that your advice is the safe route, but I think if you know for a fact you have one of the good bosses of the world then that approach can lead to better results.
In my experience, the right answer totally depends on your employment situation and your relationship with your boss and team. I think the safest answer is to try and mix things up for yourself (try a new IDE, a new stack, a new OS, etc) without telling your team. For me--and I think maybe this is ideal for most--you would have a good working relationship with your boss and you could use them to help you find a way out of the rut. Maybe that means transitioning to a new team, new project, or something else.
In the past when I've experienced burnout, I didn't get over it by powering through it. Taking time off without filling the void with something meaningful also wasn't the answer for me. I wanted to work and to stay busy, but I needed to find a problem that I could latch on to and be truly interested in. Since I enjoy learning, trying new patterns and new tools was usually enough for me. There was one past episode of burnout where I simply had to find a new company because nothing that company did was exciting to me anymore.
What I've found while working in defense is that when your customer issues a statement of work with clear high level requirements then you're going to need waterfall (even if just at a high level).
It is definitely a thing. And for big projects it can be helpful. But in most cases I think a scrum master should probably handle multiple projects if that is going to be their dedicated role.
This is pretty alarming. To me, climate change has always been real but I always assumed the effects were going to be much further in my future. Clearly I was wrong. In just the last few years there seems to have been a massive acceleration in the number of climate change-related events. How long will it take our political machines to finally be OK with addressing these problems? It has already taken too long, so I don't have high hopes. I would think an article like this would scare the hell out of coastal states like Florida. This time the ice melt remained largely inland, but one of these days we'll run out of luck.