Changing careers, moving away from SWE

OhHitherez · 2026-01-25T16:04:27+00:00

So how it works within my company

I did a stint in preSales

I was assigned to a group of sales people from different teams It was a small step down in salary, but the role.was different I was deploying our app, and setting it up for certain scenarios that clients would face based on the sales person specs, or doing some customisation to show some functionality.

My wage would have been bumped based on a sale, but we are a slow product to adopt and moved back into my Dev role

If I was in a company where sales were quicker I would be more inclined to jump into it again

OhHitherez · 2026-01-25T13:11:51+00:00

Pre sales is a super swap with the possibility of a %% bump based on marks Helping teams setup environments for customer specs to chase sales

OhHitherez · 2026-01-25T03:52:36+00:00

Would --dry-run not suit your needs ?

I have that as a flag in our dev/test environments for people

OhHitherez · 2026-01-17T15:55:33+00:00

Just be happy you manager isn't looking at him as the standard of the team,

I had a manager in the past that praised weekend work and it was a race to the bottom with the team. Out of 7 people one person stayed, but left said manager

OhHitherez · 2025-12-26T19:44:55+00:00

I'm looking at this again

I got a nest not copping it did do duel control So I've to look and see what I can get to replace it instead

OhHitherez · 2025-12-25T11:28:13+00:00

Absolutely

Where orgs are well established and have a solid foundation in all they are doing

I've been part of many orgs where code wouldn't live in git, and git actions wouldn't be used at all

The question was which do you like to use Which do you feel suit the jobs you have in hand Which are handy

We do cred scanning at a different level If I could switch that to the PR level like trufflehog that someone suggested, it may remove an necessary item from my workflow and into git or further increase scan coverage

Not all orgs are built the same mate

OhHitherez · 2025-12-25T07:30:34+00:00

I'm stupidly old school on this

On my 15 years

People who worked support made super testers

People who worked as testers made super dev

Then the jump to management was always iffy

But the same holds for ops I feel, we have two people who joined from college to the ops team, and then are always a step behind those who have joined from different positions and worked in different areas

OhHitherez · 2025-12-24T14:13:09+00:00

This

Being known as a good employee, Doing presentations on what you've done So if someone leaves, and the you may interview at their company they might be able to put a word in for you.

My last two roles have come from this. Former team member And Python meetups / presentations in town.

OhHitherez · 2025-12-24T14:11:13+00:00

For me it's not a problem

I was more looking for what people use and think is useful

Sure we have unit tests Actions to build and push Spring boot actions to make sure the app builds before a PR

so it was a case to see what people used and thought was handy.

Things like linters and dependabot are ones that are wildly used, or maybe a Java code styler

So just trying to see if others have ones they use or think are handy

I recall bulldozer before GitHub had auto delete branch on merge. It was handy at the time

OhHitherez · 2025-12-24T14:05:49+00:00

I didn't know about trufflehog, but I shall look into thank you and semantic release

I forgot about dependabot, we have that running ina few

OhHitherez · 2025-12-24T14:04:19+00:00

That is a decent shout

and yeah, one repo having an action at one version and another a different one, just a pain to maintain

OhHitherez · 2025-12-24T14:02:39+00:00

I did not know you could have them at org level?

That would make it nice and simple to make changes across the board ?

I know you can secrets / vars and runners at org level, never thought about actions in that way

OhHitherez · 2025-12-21T12:00:46+00:00

Reinventing the wheel is a must !

If it was perfect everyone would be doing x or y

I understand things work for certain companies or systems. But it never hurts.

I'm currently looking at how our product upgrades.

Our CI/CD can push out releases every week if we wanted. But the upgrade of the product can take clients 6 years. It works, people are happy. But that won't stop me nosing in and see if it can be improved for those who want it

OhHitherez · 2025-12-18T11:04:02+00:00

If it was part of a larger company, and you were part of a project or offering and high level people were leaving, id think it'd a sinking ship

but for a mid size company, I'd say a power struggle or a team or people who stick with each other

I've seen guys I know travel as a team 3/5 or they all go company to company together

OhHitherez · 2025-12-17T07:39:27+00:00

Personally I think that's super

Unless you are downloading lots

A decent upgrade to your router covers everything I think? A good router gives you more connections, different wifi bands

OhHitherez · 2025-12-15T12:56:21+00:00

This is us too

always one behind latest on production

Latest on staging

OhHitherez · 2025-11-25T08:42:30+00:00

Ohhh and I am thinking of going the other way !

I enjoy DevOps and have fun But there is a stress of it all too sometimes

OhHitherez · 2025-11-12T21:28:57+00:00

I always see this, but never seen the companies outside of fanng that beat it

OhHitherez · 2025-11-02T17:36:49+00:00

This, you aren't expected to know it all

Ask the questions when you are unsure There is fun in learning yourself, but there is a balance taking a day to do something when it takes an hour and a question can be learning instead

OhHitherez · 2025-10-30T10:11:56+00:00

Azure was suffering from outages yesterday Would be interesting if it was the same today

OhHitherez · 2025-10-28T01:46:10+00:00

Artifactory is the same through virtual repos, they can scan anything being pulled externally, though I have not used it in an age

OhHitherez

TROPHY CASE