@Wisecrack as long as I don't have to do the same for all the times I accidentally slowed things down 😅

@Wisecrack I subscribe to your rants even though I don't understand them 😂

Probably something about the lack of snow productio-- ah right

@Voxera JetBrains have WebStorm which seems to do the trick. I think their other IDEs also include some of WebStorm's functionality - I use Rider with our C# backend but also with our Angular frontend and it works great so far. Haven't had any reason to go back to VSCode for any frontend work, but then again I'm not much good at frontend...

Damn, y'all got me googling bull jizz. Turns out I was completely wrong, there's apparently a myth about it being in energy drinks but it's just a myth. Also a joke scene from Kingpin (1996). Just another day of me being wrong :)

@superdupernova agreed on the c# bit, and while I'd say VS is improving I'm still a die hard fan of Rider. One can use the early access and nightly builds free of charge, though I'd certainly buy my own license if work didn't pay for it.

Avocado? AvocaDON'T

@netikras I might be misremembering but isn't bull semen some kinda delicacy somewhere?

@hjk101 it was doing this a couple hundred times for about 10 or so references, ha

https://learn.microsoft.com/en-us/...

It was also doing it repeatedly for those same references for each process, so I added thread-safe caching to cut down on that repetition also.

@asgs damn, can you believe that, in a week, 2020 will have been four years ago 👴

Triple each estimate and make sure to drag out each ticket for exactly that long, job done

Day 7 part 2 driving me cray cray 😭

We have a dedicated table with settings as columns... So that's probably the wrong way to do it

Most likely not anonymous... One year we had to plug in a personal ID, this year we were sent personalised links so that we "didn't have to put our ID"... Because the link is the ID.

AFAIK most modern frameworks have the same general ingredients: template, style, and logic.

However whacky the templating and styling with Blazor may or may not be, the fact that you can handle front-end logic without having to touch JavaScript or typescript is an absolute win in my book. I'm with @tosensei on this one.

Imposter syndrome can suck it (until tomorrow at least)

I also read the docs on some of the libs used in that tool and brought memory usage down from around 14GB (when first getting it to run in parallel) to a couple hundred MB. Double win!

@SidTheITGuy I think they're talking more about people rather than the algorithm. People just mindlessly say congrats even though they don't actually care. If they did, they'd realise they were congratulating a dead person.

git checkout -b fix-shit && git commit -m "invert if-statements and use early returns to reduce nesting" && git push

Syntax knowledge doesn't make a good programmer, logic, thought process and problem-solving do.

I'll try and dig up some examples once I'm back at my work machine. If there's just one commit in question, sure, going through to the ticketing system is no big deal, but what happens when you're scrolling through commit history with multiple commits? Just seems like an unnecessary exercise that could be avoided if the author of the commit wasn't being lazy.

It's been a while since I've actually used it, but the setup I have is Termius to forward the VNC port through a SSH tunnel, then RVNC Viewer for actually viewing/interacting with my VNC server. This was back when I was wanting to remotely control my machine over the internet, if you're just working within your personal home network then the SSH tunnel isn't necessary.

I also realised with the last part of my previous post that even with the code comment it's less clear what is happening than if the code was written the way I described - right now I can't tell whether the comment is saying that the condition in the if-statement is validating thingies, or if the code block following the condition is what performs the validation. It's probably the latter, but could go either way imo 🤷🏻‍♂️

I kind of agree, but rather think that the code should be as self-documenting as possible. Wherever you might feel the need to write a comment... Chances are you can abstract that block of code into a method with that comment as its name.

In this case it's a bit of an extreme example, but I'd either abstract the whole block of code into a method like Validate(thingies); or at least abstract the condition in the if-statement to something like AreValid(thingies) or CanValidate(thingies).

This reminds me I need to get wakatime working on my new machine. Thanks!

In your position, I would... Just answer the question, but also explain the difference between reverting and undoing a commit. If they're still just working in a local feature branch rather than needing to revert a historical commit, it's much better to just undo the commit in question rather than revert it and pollute the history with two unnecessary commits.

@-red 'then you have to check that nothing is messed up' gives me /r/RestOfTheFuckingOwl vibes

I don't know enough about keyboards to comment on whether every single one of your requirements is achievable in a single keyboard, but I reckon the best place to get input and figure out what might be possible is the /r/ErgoMechKeyboards community on Reddit.

I assembled my own Kyria split keyboard a few years back and love the thing.

From a code review context, maybe another way of looking at it is: "the reviewer should be verifying that your code does what you say it should, not figuring out what it should be doing in the first place".

The 'you say it should' part is the commit message :)

And the other benefit of having meaningful commit messages is that it makes code review much easier - if I'm working on a complex ticket with many changes, a reviewer can review my PR commit-by-commit and verify that each commit is doing what it's supposed to, as well as then being able to look at all the commit messages to verify that the bigger-picture logic also makes sense.