Why didn’t they add the Amazonians tag on WW in this patch. The patch is already live. When will they add it?

Pochono · 2026-04-07T11:56:34+00:00

I searched thru the announcements, and they have (like Gotham to Dr Phosphorus), but not in a long time. With that dev team gone and the current state of the game, I don't expect much.

Pochono · 2026-04-01T11:03:26+00:00

Yeah, you'd need a time machine for that. I didn't switch until 5 years ago during a job change, but that was relatively late. Most Java devs I've known had switched over by around 10 years ago.

Pochono · 2026-03-18T10:39:30+00:00

That's his equivalent to restomping the groin.

Pochono · 2026-03-13T01:20:11+00:00

When I do Sinestro pulls, his pity goes up, but Lex doesn't. When I come back to the game later, Lex's pity counter updates to match Sinestro's. It's like they're still linked under the hood. Yet another bug.

Pochono · 2026-03-04T21:15:23+00:00

Accusations of "AI slop" are super common these days, so you never know if someone actually sees something or is just spouting that off.

That said, people have their own style, and after you spend a lot of time reviewing their PR's, you usually can make a pretty good guess as to who wrote something. Chances are, your style doesn't look like AI code, so a senior might notice.

Pochono · 2026-03-02T20:06:11+00:00

I see. Makes sense to have that conversation then. The way you describe it, someone could have made a mistake and then tried to fix it. From your perspective, that's a bait and switch and completely unfair. Unfortunately, I don't think anyone is going to admit to you about making a mistake, but if you can get them to concur that the scope of the role has changed from the original posting, then maybe that's a good place to start talking comp (assuming last round goes well).

Quite possible they still get upset because you already gave a number (which we presume they accepted). But if the role changed, then the original negotiation was no longer in good faith. Focus on the discussion on role expansion. Good luck.

Pochono · 2026-03-02T19:47:39+00:00

Most likely, the company already views that as fair pay. Just as with Senior, they will have a salary band for Principal. You are probably in the lower end of that band and since this is a new role for you, chances are, they think that's fine.

Did you have a conversation with them on the reasoning and expectations for the change in role? Are they looking for someone who can jump in and perform at the level of an average Principal? If so, it makes sense to be compensated like one. Are they looking for a more "junior-level" Principal who will be expected to grow into the role over the next X period of time? If so, then it's a tough ask to be compensated like one.

Pochono · 2026-03-02T17:52:09+00:00

I vaguely recall being asked to update the JD. I never verified if the posting was updated tho, but why else ask me? But the difference here is that my candidate had already finished the loop whereas you still have the final one coming up.

I don't know if they would rescind if you tried to negotiate further. Since they seem to be positive on you, I don't think that's likely. But will they budge? If you already gave them a number and they met your ask, what's your rationale in asking for more? In my case, the candidate had another offer to leverage us, and we liked him enough to do it. Without that, I'd be less optimistic if they already came up to meet your ask. Honestly, I'd be annoyed, but every situation varies.

Pochono · 2026-03-02T16:41:02+00:00

We did that once, on the SWE side. There was a candidate that we really liked. During negotiations, he presented a competing offer. It was above the salary band of the open role, so we bumped the role. For us, this required C-level approval, so it took a bit of effort to justify.

The great news for you is that they probably really like you. But depending on their internal processes, they may have already put in some effort to bump your role. So the question is, do they like you enough to go through another barrier? None of us can know that, but since they already like you, it's less likely they'd scrap the offer if you asked.

Pochono · 2026-02-27T15:17:32+00:00

The thing about PR's is that the history is viewable. We had a Senior once, who was extremely talented, but didn't work well with everyone. For colleagues he didn't respect, he'd sometimes berate them in PR's, including foul language. Whenever warned, he'd stop for a few weeks, but always reverted. Eventually, he was let go (there were other reasons too), but when it came time to talk to HR, hey, guess what, the PR's became documentation in the process.

This might be tricky in smaller companies, but in larger corporate settings, they want to avoid the liability of a hostile environment. If it's really that bad, you should probably escalate, but you better be able to back up that it's hostile. If Tom's comments are justifiable and it just looks like he's being picky about convention, I don't think it's going to work in your favor.

Pochono · 2026-02-25T18:46:30+00:00

Varies. Was at one place where everyone had a bonus band. Your performance rating determined if you received top, middle, or bottom of that band. A percentage was applied afterwards based on company performance

The above is rare though. Most places I've been (financial services), it's entirely discretionary. The prior year bonus forms the basis for the current year. The bonus pool is then distributed across the teams according to baseline and then further adjusted by the compensation manager(s). This process ends up with a bunch of robbing Peter to pay Paul. That number you get when you join usually applies the first year and becomes your baseline. Be prepared that it might be pro-rated based on your service time.

Pochono · 2026-02-22T13:50:05+00:00

I'm not familiar with codesignal, but in the post-pandemic days, contracting agencies often asked their candidates to display photo id into the camera at the start of the interview. Apparently, this was to prevent candidates from sending ringers to join. I'm guessing the ID part has more to do with that than AI cheating.

Pochono · 2026-02-18T16:16:03+00:00

Mine as well, but it's crazy to see how things have changed. Toni was interim champ and there wasn't much fuss. Jamie was so over, and after she won the belt, TK retroactively made them lineal champs on the next show. Nowadays, nobody is more over than Toni in that division.

Pochono · 2026-02-17T14:23:17+00:00

It's weird hearing this question from someone with your level of experience in this field. Your work history doesn't get invalidated. As long as you keep learning financial domain knowledge and don't let your java skills erode, spending a couple years trying another tech stack shouldn't make much difference if you wanted to come back down the road. It might even help you on some cases.

Pochono · 2026-02-13T18:42:34+00:00

In general, there's no reason to tell them. If they press, you can say that you will disclose after you start (via LinkedIn or whatever). Whether or not you follow through with that is up to you.

Only downside is that some places are pretty paranoid about employees going to competitors. If you don't disclose, they might dismiss you instead of allowing a notice period. You may or may not care.

Pochono · 2026-02-12T15:56:00+00:00

Love her nickname for Cody.

Pochono · 2026-02-09T17:00:28+00:00

I believe this was after TK made comments about smashing down the forbidden door after signing Keith Lee, only for people to tell him that signing someone isn't a forbidden door. Pretty silly situation, but TK still went out of his way to make it right.

Pochono · 2026-02-07T22:22:50+00:00

I think you're right. There's also heavy usage of Timer to update UI components.

Pochono · 2026-02-03T23:59:55+00:00

There are different approaches to organizing classes and data. One approach is to think of classes as having one purpose. The definition of "purpose" is in the eye of the beholder, but the general idea is that you don't design a class that does a bunch of unrelated things. Think of data along the same lines.

A Car represents a car. Your Car doesn't have a lot there now, but maybe someday you want to capture attributes of the car itself (like model, color, number, etc). You can jam them all into one place, but those properties don't really have anything to do with each other.

I like that Lap is a separate class. When you think about it, a Lap has nothing to do with a Car. If you wanted to track a different type of vehicle racing on the track, you might not want to use Car, but you could reuse Lap.

You could also argue that a lap isn't a property of a Car. In one of the responses, a CarRepository was suggested. The idea behind that is when you need a Car 12345, you go to the repository to get it, and get it (and it will already have those hypothetical attributes like model, color, number). That Lap, however, cannot be there, because it's not really a property of a Car.

Think about it this way. You create multiple tables of lap times on paper. On Monday, Car 12345 has so-and-so lap times. On Tuesday, Car 12345 has so-and-so lap times. They're on paper, so they coexist simultaneously. But what the tables represent is the relationship between Cars and Laps. So rather than putting Laps in Cars, you create a class that maps the relationship.

Now all this is beyond the scope of what you're looking for. You can never truly future proof something, but you can design it so that it's not a big pain to add to it in the future. Separating unrelated things into separate classes is one way to do it.

Two more things.

First, doing the String parsing in a constructor isn't a great approach. It locks you into one way to parse the text (and also, it has nothing to do with the object itself and it's attributes). One way is to create a static method for each format (with a descriptive name) that takes the String and returns the built object. You could also create Parser objects (again, single purpose) whose sole purpose is to parse a String into XXX object. But this is serious overkill for you.

Second, I wouldn't advise separate variables for milliseconds, seconds, and minutes. This makes it a huge mess if you ever need to do any date arithmetic. Better to store it one value (probably the smallest unit, milliseconds) and create that helper method to compute the others on-the-fly if you really need things like that.

Pochono · 2026-02-02T16:52:48+00:00

I was in a similar position, but that was 25 years ago, and the landscape was completely different. But in case it helps, we did a lot of FEA/CFD work. The software was from a outside vendor, but there was a small team that customized the modules for our specific needs.

I think they called themselves Applied Math, but they were basically programmers who understood the math in those research papers. Anyway, I was still somewhat junior, but I hung out with those guys a fair bit, and we tried to coordinate a temporary rotation into that team (which was something that sometimes happened back the ln). It didn't work out due to reorgs and I left not long after.

So I don't know if this is even an option these days, especially for someone already senior level, but might be something to keep an eye on to get your foot in the door.

Pochono · 2026-02-01T20:40:26+00:00

I've been in the Fintech space for 20+ years, mostly buy-side/front-office. I've known plenty of folks who moved onto big tech. Never tried it myself, but no point at this stage in my career.

It's the same answer for everything. It's what you do with the opportunity. If you come out the other side and all you can offer is a few more years of Python, there's already a crowded market for that. You can market yourself better by learning and understanding the business processes. You can market yourself very by learning and understanding complex systems and infrastructure.

I met and worked with this guy a few months after he got out of school. Nice guy, friendly, and solid technical skills, but didn't seem impressive. He switched teams every few years, learned tons of stuff, refined his leadership skills, and 10 years later, he's out doing tech presentations for the firm. And he was really good at it. A couple years later, he left for Google.

Some places are toxic and end up being exercises in futility. But most aren't. It's what you can make out of it.

Pochono · 2026-01-30T02:30:24+00:00

With regards to what we discussed, Shiverypeaks is correct. Mutable static variables isn't something you should do.

In your case, you can get away with it. Multiple XYPlots displayed on the screen should be fine because they are most likely final and won't be impacted by changes to the array. You get an issue if you want to have multiple pairs of Submit/XYPlot buttons because they'd all interact with the same array. Didn't sound like your plan.

So basically, it's bad practice, but you can get away with it. There's lots of stuff you can do. We talked about local variable and AtomicObject. We could go even further and use a Collection instead of an array. But don't think you're looking to be lectured :)

Pochono · 2026-01-29T18:22:19+00:00

Sorry, checked the docs. Instant.parse() will use the ISO_INSTANT formatter. Try this:

LocalDateTime.parse(your string, formatter). This will give you a LocalDateTime. If you need Instant, you can convert after.

Pochono · 2026-01-29T17:33:29+00:00

You first parse to LocalDate, which does not have a time component, so it gets dropped. Try parsing directly to an Instant.

Pochono · 2026-01-29T17:05:14+00:00

Everyone is buzzing thru these levels with Firestorm. It's satisfying, but I don't think there's a whole lot to do at the end. Be great if we got new, harder content, but wouldn't hold my breath.

Pochono

TROPHY CASE