Isn't that the same as modern languages? For example in ASPCore / C#, you can just register all your services with a lifetime scoped to the request, and then there's no shared state.
If you want there to be a shared state, you'd just have to register your services with a higher lifetime scope, like with a singleton scope
It is, for example, EFF has paid positions, and they're huge advocates of FoSS. "Opensource Advocacy" is not the job/job-title, but it's part of the job
Also there are companies that are FoSS at it's core - but get paid by clients for consultancy work for support and implementation of their FoSS. They have paid positions for advocacy for their software
Yea, there are more overpowered things to use with unlimited freecast, though the thing with the underpants glitch is that it takes an Action. So if you're trying to use this during combat, it's not that great.
Also with this method, killing anyone does not seem to get associated with you. So you can basically stealth kill anyone, and then walk back back in with your group and everyone around is still friendly
It's been in there since the beginning, I also would have assumed they would have patched it away by now.
There was a similar kinda bug with Markoheshkir, and they did patch that
From the screenshots it looks pretty easy to compile:
If they just ripped their entire git repos or something, and it's complete, it should be pretty easy to compile.
Edit: Compile instructions: https://pastebin.com/igt8BM4S
Yes. But are most managers too dumb to figure out that you can't program? Also yes.
He gave me one last tip. If I ever want to have a career in a management role, like CTO in the future, I must emphasize more on “taking credits” from the beginning of my career. He said being humble or modest is overrated and it would not do me any good for my career.
I don't really know if any of this is true, or what the context is. Maybe this is how it is in American Corporate culture, but it's not really how I experienced it.
If you're a beginner programmer, sure, you can brag about how cool your code is, and how much you've build. But if at some point you become a lead developer and you're still doing that, it seems kinda toxic.
As lead developer in the standup or reports I'd usually downplay what I did - like instead of saying "I build this cool new feature" - present it as "The backend team build this cool new feature". If someone else build something cool, I would specific say something like "Bob build a really cool feature"
I must emphasize more on “taking credits” from the beginning of my career. He said being humble or modest is overrated and it would not do me any good for my career.
A good Team Lead or CTO needs a good team, and the team usually appreciates it a lot more if you're spreading the credits around instead of taking them for yourself.
Besides that, a random developer in a big company is very unlikely to just become the CTO by not being humble. If you want to become a CTO, you either join a startup or start your own company
I don't know if this is a relatively "new" computing paradigm, though if you compare it to the pre-2010 area, its pretty much the standard for bigger applications. And I think it's very much tied in with the Move to Cloud Computing paradigm.
In the good old days everyone just had their own servers running somewhere, so what are you going to do when its super busy on your platform? Add a new server for a couple of days? If you have a new server anyways, you'd just permanently add it to the network.
With cloud computing, as you mentioned, there's Service orchestration like kubernetes, auto-scaling of bare-metal machines, and Serverless Applications that just keep track of usage and allow you to very easily temporary add more power based on demand, and upscale your infra for the time that it's needed.
If you start getting into paradigms like that, you might end up with 100s of services running at the same time (multiple copies of the same services for load balancing, or edge-locationing etc) - Then you also don't want to put cross-cutting like logging and analytics hard-coded in every service like you'd potentially do in a monolith. And you need those kinda metrics to see that everything is still running healthy, and to automatically kill unhealthy services to replace them with new ones, etc
Just wondering, what's the purpose of the logo / where is it shown? If the logo is just the favicon - you could create a very elaborate logo, but it doesn't really show up in a 25x25 image
I've been developing an AI tool, and I've generated a lot of images for testing purposes that are pretty much in the same sentiment as this picture:
I don't really want to spam this post with lots of pictures, so here's a collection of attempts: https://imgur.com/a/F6Kc26O
I think they're either Dalle-3 or SDXL based, but with a lot of customizations trying to fine-tune it
Cool, how much of your 25 years was to "write test automation to test the front end" full time?
This guy is in his 3th job after 6 years - so job-hopping every 2 years (as per the current programmer-job-meta. - ) trying to find the right job that fits him - but obviously he hopped into a disaster of a job. Its a personal anecdote of his experience so far.
If you have 25+ years of experience, but you can't relate at all to what he's experiencing, then this guy already has more experience than you do
Maybe one of the 1800 disgruntled ex-unity employees that got laid off this week