The AI tools are honestly so useful though…

I like the idea, but I can’t come up with any method that won’t devolve into most reviewers only checking the highlighted parts tbh.

No, this is actually the first time I’m hearing that this exists unfortunately.

I was obsessed with making variations of it on TI calculators in high school lol

I think someone else said what it actually is in another comment. It’s functionally identical 90℅ of the time for me anyway,and I use CLI and vim on it.

It works fine for small projects. I think that with more than 2-3 devs a PR based strategy works better for enforcing review and just makes life easier in general, since you end up with less stuff like force pushes to fix minor things like whitespace errors that break everyone’s local.

If it’s a private repo I don’t worry too much about forking. Ideally branches should be getting cleaned up as they get merged anyway. I don’t see a great advantage in every developer having a fork rather than just having feature/bug branches that PR for merging to main, and honestly it makes it a bit painful to cherry-pick patches from other dev branches.

Everywhere I’ve worked, you have a Windows/Mac for emails, and then either use WSL, develop on console in Mac since it’s Linux, or most commonly have a dedicated Linux box or workstation.

I’m starting to see people using VSCode more these days though.

I didn’t realize just how siloed my perspective may be haha, I appreciate the statistics. I’ll agree that cyber security is a concern in general, and honestly everyone I know in industry has at least a moderate knowledge of basic cyber security concepts. Even in embedded, processes are evolving for safety critical code.

… You know not all development is Internet connected right? I’m in embedded, so maybe it’s a bit of a siloed perspective, but most of our programs aren’t exposed to any realistic attack surfaces. Even with IoT stuff, it’s not like you need to harden your motor drivers or sensor drivers. The parts that are exposed to the network or other surfaces do need to be hardened, but I’d say 90+% of the people I’ve worked with have never had to worry about that.

Caveat on my own example, motor drivers should not allow self damaging behavior, but that’s more of setting API or internal limits as a normal part of software design to protect from mistakes, not attacks.

My take was that they’re talking more about a script kiddy mindset?

I love designing good software architecture, and like you said, my object diagrams should be simple and clear to implement, and work as long as they’re implemented correctly.

But you still need knowledge of what’s going on inside those objects to design the architecture in the first place. Each of those bricks is custom made by us to suit the needs of the current project, and the way they come together needs to make sense mathematically to avoid performance pitfalls.

I was gonna say, the OP here sounds perfectly good at computers. Most people either have so little knowledge they can’t even start on solving their printer problem no matter what, or don’t have the problem solving mindset needed to search for and try different things until they find the actual solution.

There’s a reason why specific knowledge beyond the basic concepts is rarely a hard requirement in software. The learning and problem solving abilities are way more important.

The Adobe photography plan costs me $120 a year, and honestly includes more useful updates than not. Their AI masking upgrades the last couple years are saving me hours to days of editing time per photo session.

$120 a year is worth maybe one hour of my free time. Even just migrating to Darktable would take me weeks or months of dedicated time to migrate my existing catalog.

W

I’d honestly prefer they just make the battery thicker to match the camera depth. Solve two problems at once.

~220% total comp for me last year, switching companies from a job with okay but below market pay, and becoming a senior software engineer in the move. I think I can feasibly double one more time if I try, but it’d be a bigger push and likely involve working for FAANG. Anything more that is outside my reasonably likely career path.

5. Adobe software. Honestly they work, and work well.

I’m very happy with my Garmin Epix (gen 2). It’s got a nice AMOLED screen, which works better for me cause I’m honestly mostly using it indoors, and I don’t really need 50 days battery life or anything like that. 13 days on pretty high settings is plenty for me…

The watch has its own built in GPS antennas, and works fine without a phone during activities, since I saw you should about GPS stuff elsewhere in the comments. I’m pretty sure it needs to sync data to a phone eventually though, for full functionally.

This is probably overkill for you, and you can get one of many much cheaper options from Garmin since all you care about is heart monitoring.

Apple watches are the only ones I know that do the full EKG thing if that’s something you’re interested in, as far as other options. If you already have an iPhone, I’ve only heard good things about the watches too. Pretty sure their adventure watch only really loses to Garmin on battery life.

1. Setup my vimrc.
2. Clone the project, and realize that whatever repo managing system they started using 3 years ago requires setup steps not in the README and breaks everything at the slightest touch.
3. Build the currently relevant project in whatever build system they started using 3 years ago (CMake is quite nice).
4. Fix my vimrc to be compliant with whatever tabbing they use.
5. Realize that for some reason, someone made a commit in the file I’m reading that uses 3 space tabs. And worse, someone approved that PR.
6. Make changes via vim.
7. Debug via print because setting up gdb or JTAG on embedded systems is usually more effort than its worth.
8. Realize it’s a timing issue and reluctantly go find the JTAG debugger.

• Pixel 7 Pro
• Adaptive charging at night
• Somehow this phone’s GPS loses accuracy to outside of 1 block every few days and needs to be “fine tuned” again in G maps