For 10 years people asked me why I stayed at a company that had a lot of problems.
10 minute commute that’s why. You can’t put a price on it
(And it was actually a good company)

You have to move to something closer. I’m currently at a 45 min one once a week and that’s more than enough

If you want to be a lead then maybe it’s worth staying, but it depends how much you need the money.

Funny that I keep being made lead and I fking hate it.
Personally I’d take the raise and drop down.

But if you enjoy leading that’s different

It was brilliant. Best party we ever had while we waited for the world to end.

Also rinsed overtime in the run up to it when banks were simulating Y2K and needed on-call support. Never got a single call.

If you’re not sure you’ll even get into gaming then go for Xbox because you can pick up games cheaper (cdkeys for example)

Or you should go for an Xbox One X and hit the used game market.

Don’t you have an end date if you’re leaving?
So you work until you’ve left, and when you’ve left you no longer work.

Don’t slack but what work gets finished gets finished. What doesn’t get finished isn’t your problem.

@xcodesucks

Yeah maybe. There have been times when people have said “I would’ve never thought of that”.

I just meant the return on investment I got from learning OO was more than from learning algorithms.

I do find that stuff far more interesting than I used to now though and they can be fun

I’ve been industry almost 30 years and never ever been asked a Leetcode style problem.
I’ve worked at 9 companies and interviewed at more.

I’ve found it far far more valuable to understand good software architecture and OO.

@b2plane yeah I’d say I’d overkill too

Kafka is a little different because subscribers don’t take messages from the queue in a way that removes them when they’re delivered.
Instead each subscriber maintains a pointer to where they are in the queue.

So if you were to start up a whole new subscriber, it would start at the beginning of the event stream and get messages other subscribers have already read.

I went consultancy so I can find good places and maybe go perm with them one day.
So far all I’ve seen are horror shows and been thankful I’m not perm there

@Shardj I feel your pain

Going thru this right now. I feel your pain

And throw in a HDMI socket too

28 years here!
All that advice about having a 2 page resume is impossible to follow

@Oktokolo great insight and wisdom

@TrevorTheRat and Fk knows why the devRant app posted my rant as a comment to this one

Watching a presentation on using AI to write code for us.
Devs are buzzing over this. They love it.

I feel like an odd one out. I’m not excited to use a tool that dumbs down my job (tho I admit some parts of it a bit dull).

As soon as it’s good enough and the tipping point arrives, salaries will plummet before eventually someone realises that non-devs can just describe what they want directly without the devs doing it.
Analyst/AI Jockey will be thing.

If I was starting my career now I’d be wondering whether or not it’s better to move into something more physical at this point that AI can’t mimic for a while. Like bricklaying

If you take a step back to do something you want to do or get you where you want to go. Then that’s not a step back. It’s a step forward

Never work for a company where a director or manager wrote the code.
You’ll be powerless

Got my first role at the end of a work placement for the course I was doing, I was 17 at the time.

I f*king love this

He’s a lovely guy too so happy to help him out. But alarm bells were ringing that day lol

Just had this guy say to me “so to resolve conflicts I always choose the option on this side of the screen”

Oh shit.

Sounds like you need to take a step back and reevaluate what you’re doing.
Think about why you’re having problems - is the architecture the problem?, do you need some training time?, are the stories you’re working on clearly defined? Are the goalposts being moved?

Stop for a day and work through these questions (and others I’ve not thought of). Also look into ways you can iterate and deliver in smaller sizes - what is the real MVP of the product and what is the MVP of each story

Those who excel at software are more often than not promoted into some sort of leadership role that is supposed to enable them to spread their experience and wisdom.

But I’m becoming increasingly convinced that idea is just a fallacy. There is more than enough resources out there for anyone who’s interested in bettering themselves, to go and find out how and make it happen, it doesn’t even cost money. All they need is the will to do it.

All that is happening in our industry is the the good senior engineers are pushed sway from of the work they excel at, leaving behind the not so good “experienced” seniors who then frustrate the good up and comers.
It’s rare that a company keep people doing what they do best.

Cats on calls is actually encouraged at my place !

For a document db I only have experience with MongoDb. This is completely different to my feelings about DynamoDb, I absolutely love working with it.
It’s very good provided the data you store is organised with some thought. What I mean by that is, if you’re working on a relational db and the system access pretty much every table directly, then that won’t translate well to Mongo.
But if you are working with an object hierarchy that is organised into aggregates, then that translates very well because a document closely meets the idea of an aggregate.

You can join across collections, but it’s not called a join as it works differently. It’s a ‘projection’.

And you can query, there’s a syntax to do it but it’s not traditional sql.

The system I worked on was very very fast and we never had to resort to using a projection or other techniques.

Best way I found to understand it was to do the free Mongo University online training sessions.

NoSql is split between document stores and key-value stores, maybe more.

I’m not sure why a key-value store would be a good choice for an app (aside from for obvious key-value data like caches) but it is used.
When I was forced to use one (DynamoDb) it involved using the Adjacent List Pattern to access data and simulate joins.
It always felt a bit clunky to me and I don’t think it would ever be my first choice.

Jekyll and GitHub pages isn’t too bad

I swear I’ve been on this project