Drawing, Really enjoy just grabbing the ipad and creating things. It's amazing how 2d shapes can trick the viewer in actually understanding what you've drawn.
Got a background in 3D and Programming, but I think the 3d industry has the same approach to problems as programming. Couple of frameworks and libraries and poof, you have an applications.
In 3d you grab a render engine, a light setup, some assets and poof, you have an image/game/animation. I miss the days that I 3d was exploring and experimentation. The alternative would be to dive into 1 subject (modeling, rendering, lighting, FX etc). But in my experience that just made me feel like a factory worker. Piece of concept art, here you go.
3D can really trap you into polishing a soulless turd, so I'm learning drawing. where you can't cut as many corners and enjoying the creative process again.
On the programming side I'm just enjoying work and learning on the job, also going back to the fundamentals like shell, sql and regex. It's amazing how much you can automate.
Countries are talking about gambling packs that you can buy for different games. Although that is an issue I'm more worried about all the other things those companies do. Especially BR's are incredibly toxic and addictive. The random aspect of each round, not knowing if you will land on the ultimate gear on drop, or having to fight tooth and nail with scrapes and still turn up victories I think is way more addictive then currently on the radar of those countries.
Besides that all of those F2P games make you invest in their ecosystem. Battle pass here, skin there. Free unlocks when you play certain game modes. That is the real crack, including unhealthy conditioning.
So if you are working for companies like Respawn, EA or Epic (or similar). Scratch yourself behind the ears. I would say I don't have an addictive tendency, but the amount of effort it cost me to get away from apex is higher then I would like to admit. I noticed playing those games didn't made me happy anymore, but I still felt like I've invested so much in it that I had to keep going.
I'm happy that the game had so many terrible design choices for me to make it easier to step away. But the moment these companies figure that out as well, I think they will trap even more customers
wow this is really awesome. Actually was look at creating a novelty device for myself. Steam controllers touchpads, logitech MX's scroll wheel. ps5 haptics. Buttons with a great tactile feeling.
If anyone knows community that like building things like this, I couldn't find anything. (mainly because i have no idea if it has a name)
I don't really see what this article nails. So, if I understand the argument correctly. Microservices were used to increase development speed. While old pieces were left behind (legacy) new systems have come up to modernize (these are still microservices)? His team, now responsible for many, legacy unloved old microservices, are being merged back into a monolith. The real question is, is remerging all the code back into 1 application the right solution for their problems they had with stability.
I think mental models are important, and having a huge blob of unrelated roles, makes sense to the current development team. But won't, just like the old situation, to the new developers.
Perhaps it's just the clickbait article, but a better title would have been. "Homogenizing our wild-west legacy microservices".
For me personally microservices was a god send, working on getting stuff done, instead of dealing with ancient code that doesn't reflect the current business anymore.
I still buy in the thought of, if you can't develop a great monolith, you sure won't be great at building microservices.
modular-monolith is the cool thing currently. Create a Monolith, without the shortcuts that create problems in the long run. Public interfaces are your most valuable pieces in the system. Worship them, code-review them, fight about them. Currently I could care less about the implementation itself. Does it solve our problems, is it fast enough, is it tested great, ship it. What language you used, architecture. database, I don't care. Just make sure it's a joy to use from the outside.
If more developers would spend longer on thinking about the problems and less with throwing large amount of code that makes them feel smart. Making a microservice doesn't fix that problem.
Think that what is missing is the stability that microservice are able to give in its most optimal form. Each service being the main source, the second it leaves the system it is stale reference data. Is stability important? use the old reference data, how fresh does your data really needs to be.
Got a background in 3D and Programming, but I think the 3d industry has the same approach to problems as programming. Couple of frameworks and libraries and poof, you have an applications.
In 3d you grab a render engine, a light setup, some assets and poof, you have an image/game/animation. I miss the days that I 3d was exploring and experimentation. The alternative would be to dive into 1 subject (modeling, rendering, lighting, FX etc). But in my experience that just made me feel like a factory worker. Piece of concept art, here you go.
3D can really trap you into polishing a soulless turd, so I'm learning drawing. where you can't cut as many corners and enjoying the creative process again.
On the programming side I'm just enjoying work and learning on the job, also going back to the fundamentals like shell, sql and regex. It's amazing how much you can automate.