cakes

Not that it is implied but it isn't just the "summer intern" that needs some coding convention guidance sometimes. It can be as useful as coming onto a project and at least you have some chance at (mentally) parsing the code/project without a huge melting pot of styles across all parts of the project (you'll obviously still get some but with convention you at least start from a slightly better place).

I was recently trying to do something similar and looked/tried go as a solution but I ran into some initial issues around my own confidence that the shared lib would work and that I wouldn't eventually really mess up the deallocation step.

Yeah the VBA in Excel isn't .NET at all. Which makes it even harder to take something that was VBA in excel and trying to utilize it somewhere else (e.g. a .NET add-in to Excel or using any of the Excel interops via something like C#/VB.NET)

I usually am explicit in saying something along the lines of "Can it be assumed that I know how to do argument null checking, if possible, and not pollute the whiteboard?" and I've gotten a "Yes" and then after writing the function on the whiteboard: "Well what about <something relating to argument nullability>?"...so you should ask but YMMV

Agreed - something I've personally seen drive such a thing in some people are plans/checklists/etc (nothing wrong with having these) where the recognition of severity is overriden with checking as many boxes as possible in an 8hr day as is required.

I would generally agree more along there lines. I've had a manager (not lead but enough to say this) where favorites were played (friends for like 20+ years) and it is frustrating in many ways (e.g. lobbying for your friends to get different benefits within the company during their hiring, first person to seek opinion from and then move in that direction regardless of others, etc.)

I would happily work amongst a set of friends but not where it goes into leadership.

This mirrors the experience I have as well. I (currently) don't know what will cause Hibernate to flush but I certainly do know that I had to know this exactly and had to do some really painful debugging at points. The worst one I was on was just early prototyping of an app that used Hibernate and we had so many problems with performance and Hibernate(isms) that the whole thing seemed destined to fail even though our use case was exactly what ORM/Hibernate are for...yet we still have to control when changed flushed because otherwise things would get wonky really quickly.

I feel like I'm missing a partial context but "You can change all of your passwords in 30 minutes tops" is not true. I have a minimal amount of accounts (I close accounts I don't use) and I can't imagine it taking me less than several hours of slogging through it to change all my passwords (e.g. updating password database, 2FA confirmations, making sure I don't lock the account I change the password on, etc.)

So I have to aim for the clearly impacted ones from this (if named/discoverable) and then have to decide how vulnerable I feel and whether I should go through the extra effort (or not) for every password I conceivably have.

Generally agreed. I know that my priorities for what should be done in systemd are not going to match someone else's but there are also some clearly problematic things that just seem to go unaddressed no matter the scale (e.g. rebooting nspawn containers [1], problems with DNS/resolved [2]).

systemd can do a lot of really useful things but when I can't reliably reboot machines or struggle with resolving things using DNS...it's hard to be optimistic.

[1] https://github.com/systemd/systemd/issues/2809 [2] https://github.com/systemd/systemd/issues/3649

I very much enjoy using D and want it to succeed but this statement along with finding "everyday uses" for things (e.g. using zeromq) are huge drawbacks to buying into it. I'll still advocate but it's not easy sometimes

Agreed, fancy and clever in optimization/design is super dangerous especially since you don't know what will/won't work until you measure. Also if you do "Wrap anything weird in a view" (which is an acceptable approach) realize that any and all of that part of what you've built could be the problem.

The best query plan can look good even on a representative data set but your customers don't always have representative data sets and they don't really care if it works on the bench with 10 million records if their 10 million record data set does not work.

Entirely agree. Sometimes it is a feature (and sometimes a curse). Even uptime is a good point for why you couldn't "upgrade everyone" together.

At the same point if I were hosting something for a group of parties (at my own expense/will/etc.) and I want everyone to just be at version X.Y.Z - having to upgrade each deployment itself is definitely a pain.

Not all software needs to be multi-tenant but it also isn't something that is no longer needed or without thought.

Multi-tenancy solves some problems around maintenance and upgrade paths that are hugely beneficial when you are managing multiple deployments. If you have even more than just 1 deployment of a thing and scale to 2 (or N), you now also have to manage the software level of those N containers (without multi-tenancy) vs. just 1 deployment for everywhere.

While I have this same feeling, I think we (jointly) suffer for everyone wanting different things. I'd like a smaller (13" ish) size laptop with a handful of ports (e.g. 2x USB-A, 1x NIC, 1x external display port of _some type_ - that's it) but that's not everybody's "thing". I am definitely of the opinion, though, of having a functional thing over the "latest and greatest" (looking at you USB-C).

I've had "assigned" mentorship at places (which is understandable and I have no immediate complaints) but I feel, personally, being in a supportive environment of coworkers is as good, if not better, than pure mentorship.

Something like phabricator is always a reasonable choice

https://www.phacility.com/

I also initially used rss2email but ended up spinning it slightly for my own needs. It's a excellent tool to get over the first barrier of rss -> email though!

having a laptop currently (Latitude 7370) which has only one "classic" usb slot...I'd kill for 2...so having none would be even harder. It comes down to doing the simple things like using USB flash drives quickly without immediately needing a dongle.

I had a similar experience and it seemed like they were both being developed by the same core group(s) dividing their time between both (again, my perception) which was confusing as they were very similar.

I should really read more of the git doc but at least I learned about aliasing in the gitconfig from this even if, I too, was expecting actual git commands

The best/closest I have is that where I once worked, we had a NetApp that allowed it to be upgraded to a version that it didn't support (it wouldn't boot) which was not how it was supposed to be... Anyway, we should've been able to fallback but the jump we tried to make screwed with paths to the bootstrapping/startup and while normally the previous version should be recoverable...well it was not because of where the upgrade process failed.

So we were trying to recover it and I had a "It's a Unix System, I know This!"-moment and was able to manually type in the path to the previous binary during an emergency/rescue prompt (based on deductions from forums, the current failed loading message, and some obvious things like architecture) and got it up and going again.

Documented that, internally, to the best of my ability.

It potentially depends on the data and volume of deletions (and maybe other factors). How hard is it for users to recreate? If you select 30 days what happens on day 31 when a user "just gets back from vacation" (or similar)? Maybe deletion should be hard enough (e.g. Trash Can + Dialogs) that requesting a restore isn't something you'd have to do (except, maybe, in extreme cases)?

If you have to pay more than you would to normally commute, they should compensate you for the travel expenses.

Personally when a company goes through the effort of organizing an interview (especially with travel) and I get there and some amount of chaos/disorganization is apparent I get extremely cautious and is a big red flag for me. Nothing like flying across the country (paid for) to arrive and have the person I'm interviewing with change and leave me waiting in the lobby 30 minutes.

Which you'll be reminded of again when DST rolls around.

Especially since in C# as soon as you are doing this it involves a lot of inconvenience, odd syntax, and is going to not be popular internally.

Same thought but adding that if it's causing you stress/impacting your life - factor that in.

As reference there are/were tools in something like MSSQL for dealing with XML.

In relation - I've always liked the "Chaos" value from msdn for their IsolationLevel enum

https://msdn.microsoft.com/en-us/library/system.transactions...

Similarly this is why, in some places, people report having "that old XP machine running <software> in the closet" because <software> is really important to them and they have no path forward (it doesn't support > XP, it's actually too vital - though that seems like an odd reason not to update, etc.).

You could replace these things with something newer but the concerns by various parties can outweigh the willingness to fight and you probably don't want to be on the receiving end of "I told you so".

Hopefully there aren't too many enterprises out there with [domain]\user[0-9]+ type definitions!