mneil

We already see it doing that. But that's not why it's unpopular. It's unpopular because it's a half-assed rollout that is mandated for use that complicates the job further.

Managers are using AI and proclaiming success like Claude does when it confidently "fixes a bug" but leaves everything else broken.

I like AI. I enjoy using it personally. I even find it helpful at work. But, I hate the way it's being used by most people around me.

I do not work for US Bank.

https://web.archive.org/web/20260314074025/https://www.reddi...

The tax code says you can't capitalize the cost of software because it has immediate value. Not to mention that SaaS billing is the way it is to get around this. People do not have immediate value for R&D so the government allows the cost to be capitalized (ie: deferred over time) to promote hiring more people to help a company grow. If you allow capitalizing AI then you promote the adoption of AI to replace the people for the R&D, the EXACT OPPOSITE of a public policy that exists to promote workers.

What are they even thinking? Certainly not about the reason the policy exists in the first place.

This is pure propaganda. Just keep working. Feed the rich. You're just lazy.

I'm more likely to end up permanently disabled after being conscripted to war than I am to end up in her shoes. I'm 40. Gen Z is onto something right with work life balance.

A2A (Agent-to-Agent Protocol) focuses on agent collaboration. It establishes ways for intelligent agents to discover, communicate, and cooperate with each other, allowing different AI systems to work together like human teams.

Taken straight from this article:

https://a2aprotocol.ai/blog/a2a-vs-mcp

Nothing is failing. Bro likes the office. He thinks everyone should too.

"What does that mean?", I wonder. I also find it odd that someone would say it when I meet them. Am I being insensitive? Maybe.

My point is a relationship/friendship is an agreement. I like you. You like me. Let's be friends. I'm not going to like you more or less because you're on the spectrum. I'm also not going to try and discern what you're thinking or why you are the way you are early in a relationship.

All this is to say, no, I don't think it's appropriate to bring up early on. You're either inviting pity or provoking disgust (or somewhere between these two extremes) in the other person. Just be who you are. Either people will like you, or they won't.

I meet a lot of people because of my kids. I'm friends with very few of them. Not everyone is going to like each other that much. And that's ok. You'll find people who really enjoy your company regardless of any medically defined condition.

That's all you need. Tour go, and go by example.

Go is far from java. There aren't 10 ways to do things, it's not object oriented, and things like build tools, dependency management, formating, and tests are all baked into the core.

It's a relatively simple language that uses structs and relies heavily on the adapter pattern and composition. You should have no problem learning it quickly. Most go projects will look the same, have similar structure, and all will use the same formatting required by the compiler.

Kirby and the forgotten land has a second player that takes damage but respawns is they die. Items like food can be shared which makes for a really mechanic where the two of you can celebrate a health share when eating.

No reload heroes allowed players to save each other when they "die". It's a generator dungeon crawler with lots of replay time for fairly cheap.

Unraveled two literally allows you to carry the other person. Admittedly some parts require two players and may be frustrating at 5.

Mario kart 8 is amazing for young kids. Options exist to self propel and keep your kart on the track. You can set you controller down and still finish a race. The colors, music, and powerups are all appealing.

Minecraft. Both my kids started around 5. Peaceful mode, help them learn to build. By age 7 they will be teaching you how to play. This game goes deep but starts shallow. There's a reason it's so popular with kids. I love it as well.

CAP theorem gives the database of money transfers the ability to be consistent, partition tolerant, or available. Pick 2. All banks choose consistency, they have to. And partition tolerant is the obvious second choice so you don't magically lose all you money during a server crash.

If you're thinking someone can withdraw money in one country and do the same in another country would it figure out the correct balance or could you trick it? The answer is you cannot trick the ATM.

You usually can get by with 4th normal form but go wild, take it to 11 and it's all you should ever need.

This one looks like a good intro https://www.amazon.com/Understanding-Communication-Theory-Be...

And I read a much earlier edition of a book called "Gendered Lives" that had a big impact. Gender communication goes into how men and women communicate differently, why that might be, and it helped me understand other people a lot better. It made me feel less like a weirdo to know that everyone else is kinda the same :). Or, at least, that you're not alone in being the way that you are.

The problem isn't always other people. I'm an introvert, I shut down in groups, and I get anxiety in large gatherings.

I don't know what will help you. For me it was getting a degree in communications. I learned how to deal with other people, how to read their body language, how to give speeches and presentations, and how to communicate effectively through writing. It pulled me way out of my comfort zone.

Learn to communicate your issues more effectively and more people will listen (rather than argue). This makes your job easier. It helps motivate others around you. And it may even help you like other people a bit more.

Things I miss about freelancing: - freedom. I work from home now and have flexibility. But flexibility is not the same as freedom. I would take off a month straight. Or blow off a week with little notice. As long as I managed my customers expectations I could do these things. - varying work. It was much easier to dip into new tech or go after work that stretched my skills constantly. I think I became a much better developer and a much better person overall because of my years working for myself. - being picky. If I didn't like something I didn't have to accept or pursue the work. Sometimes now I get directives that limit me or my team from doing the best we can and I'd love to say, "I'm not doing that"

Pros of the in office job: - coworkers. First, make sure you like them before you start. Bring next to other smart people can help you long term. You can make strong bonds that help you advance your career. I've worked with one person I met in one job at two other jobs now. People change jobs, knowing people is half the battle. - social activities. Freelancing is isolating. Yes, go to meetups, go to conferences, join groups online. But it's still not the same as, "I'll see these 10 smart people every single day and can talk to them at will"

I'm now regular job but fully remote. Benefits: - you get to work with smart people. But you have to very outgoing and constantly teaching out. I'm a bit of an introvert. I've had to learn this skill. Freelancing 100% helps here. You also need a good team who is also not afraid to communicate. - flexibility: I mentioned this already but I take my kids to school and pick them up everyday. During the pandemic I monitored and kept the kids on track during home school while my spouse was at work. You can't do that in an office typically. I can split my day or take a long lunch and nobody cares. - super smart people. The smartest people I've met have been during remote working (I'm 3+ years in now. 2 different jobs). It's not always like this. But remote jobs tend to try and find the best from anywhere. And when that is successful you will benefit from knowing those people.

I have happened to switch jobs roughly every 3 years. Freelancing was nice because it was a solid 7 year block where I could say I went from gig to gig and nobody bats an eye. With office jobs people start to question if you go from place to place in less than a years time :). I've found switching jobs to be the best way to learn the most and continually get higher pay. Each job I take I hope will be the one good enough to keep me around longer. If you're not learning at your current position, and you've stuck around for 2 years or more, then switch.

Oh, why did I initially switch back to a day job...

2 things: freelancers rarely get to stick around for long periods of time on big teams to build cool things. I was either solo and building a medium sized app or would work in a small team building something slightly bigger, or a large team where I'd build just one part. Working full time you get to see big projects start to finish.

The job itself. I was looking for freelancing work, found a good company, they wanted me full-time and I really liked the team and the work.

Stability of pay. I am married, have 2 children, and own a home. I did that all while freelancing. But my stress was reduced when I stopped having to constantly look for my next thing.

People, scenes, animals. Both realistic and stylized.

Time. Art is as much a trade as anything else. It takes constant practice to get good and maintain it. Software paid better than art.

I have a bachelor's of arts, in art. I would draw, paint, or create for 20+ hours a week, every week, for a couple years. I also have an associate of arts in graphic design.

Ultimately, I do not practice anymore because I love programming too, it pays better, and there isn't enough time in the day to be great at both.

These are all fairly common terms I see or use for these scenarios.

There are a other terms you could use though in different systems that make sense.

Master: main/primary/broker Slave: agent/worker/replica/node

Bust out a thesaurus. Ace is apparently close to master. I kinda like that word. Ace of database.

That said, the shutdown is government mandated. We're completely outside the spectrum of capitalism at this point. There is no free market when the government intervenes at any point. Since the feds shut it down it does make some sense that they also prop it up.

Avoid managing the underlying os as much as possible. Use vanilla or prebuilt images to deploy these containers on, coreos, Amazon's new bottle rocket (maybe). Or use a service like fargate when possible. All configuration should be declarative to avoid errors.

If you need to build images tools like packer are great. AWS has a recommended "golden Ami pipeline" pattern and a new image builder service if you can't use community images.

I'm speaking imperatively but read these as my own directives. I work for a company that consults and actively helps fortune 500's migrate to the cloud. So some of what I'm saying is not possible or harder on prem and I recognize that.

If I had to, I still like Chef, puppet second favorite mostly because of familiarity. Ansiblee can be used with either of these. And tools like serverspec to validate your images. I don't really use any of this anymore though.