halloween_spookster

Blockchain is just a ledger. Most systems don't need a ledger, they need a database. It was a solution looking for a problem in most cases and the marketing/business types don't listen to the engineers if the engineers are even in the room.

When I interviewed at a company some years ago, the commute would have been ~an hour on a normal day (potentially longer if I did park-n-ride). I was very forward about wanting to only come into the office once or maybe twice a week. The manager I was talking with brushed off my commute time by basically saying that the commute wasn't that long and he knew others that commuted much longer. That was a huge red flag for me and I did not proceed with them. I don't care what others will tolerate. If management is going to ignore concerns like that, I don't want to work there. It was really apparent that he wouldn't let me work from home more than maybe once a week if I was lucky.

One of the things I've always remembered about Decent was when you put in cheat codes it would play a little sound effect of someone saying "cheater..."

How do you view yourself/your decision looking back? Do you have any regrets?

Is it a direction you would recommend for others?

What is something that the average person doesn't know about stripping that you wish they did know?

Are there any particularly interesting or funny stories that you want to share?

Putting question marks or exclamation points after "quotation marks"! I've never understood the point of putting the punctuation inside the quotation unless it's part of the quotation itself.

It can vary a lot depending on the day and the company/job. Frequently there are meetings that are update/planning discussions, discussions with one or more other engineers on how to build a given feature, debugging existing code to figure out why it's not doing the thing we want (which is a different but overlapping skill set with coding).

Ultimately there isn't really a "typical" day because we wear a lot of different hats. My current job is more coding heavy because I'm at a small startup with only a couple of engineers. In a given week I'm probably doing 10% meetings, 50% coding/debugging/configuration, 20% code review (reviewing other people's code), and 20% thinking/designing/experimenting with ideas. Those numbers vary a lot though. At a previous job I ended up spending an entire week just doing project management to alleviate my boss' anxiety over a project (which was somewhat self defeating because it meant I wasn't getting work done on said project). That job in particular had a lot of politicking and communication which was due to micromanagement.

A lot of what people don't realize is that we aren't just building a feature. We're building a feature while thinking ahead to known or potential future features. How can we build feature A to enable making features B, C, and D easier/better/faster without also making feature E much more difficult or impossible? It's about building flexibility into the system while also balancing against time and cost restrictions. We as engineers have things that we see as necessary while the business wants more features and it's necessary to balance the two. At a healthy org that means that there's a negotiation of priorities between the two forces. If you only focus on the technical stuff, you won't ship features. If you only focus on the features, how fast you can deliver features will come to a grinding halt. Your system will also start breaking in unexpected ways which takes time away from building features.

It's kinda a rambly response to your question but I hope it helps.

Software engineering.

Most people don't have a clue what we do. Especially management. Most people think we're code factory workers, just writing code all day. In reality, it is closer to being an artist than it is a factory worker. There's a ton of thinking, discussion, design, and unfortunately politicking.

Idle games/games that have an idling mechanic

Bake him away toys!

I've been playing Factorio with a friend. Our factory was getting large enough that him downloading the map and catching up was getting really slow (even though the factory itself wasn't that big). We ended up setting up a VPN which somehow made that process SIGNIFICANTLY faster. However, I really only wanted the VPN on while we were playing the game. So I ended up writing some automation to detect if I was no longer playing and the VPN was still active and then shut it off automatically. It's a small thing but I'm both proud of it and happy with the results.

I don't remember much of the specifics, but I remember it was with Dr Medico's alternate. It was something about being healed by the rest of the team which turned into damage that was redirected (and enhanced) where we wanted. I remember being able to do ~50 damage in a single turn.

I love Sentinels! A friend of mine and I actually found an apparent game-breaking combo a few years ago. We defeated one of the harder bosses in I think 2 or 3 turns? It really felt like we were doing something wrong but we couldn't find anything.