StudioLE

joined 2 years ago
[–] StudioLE@programming.dev 2 points 2 years ago* (last edited 2 years ago) (2 children)

You can long rest pretty much anywhere out of combat so does it make any difference when you can prepare?

[–] StudioLE@programming.dev 27 points 2 years ago (7 children)

The obsession with Shakespeare puts a lot of students off literature

[–] StudioLE@programming.dev 7 points 2 years ago* (last edited 2 years ago) (4 children)

How many people are actually returning this product though? Nobody is going to any effort to return a product that costs so little.

And everything I've read about this recall makes the reason clear so I can't see anyone opting not to just consume it - which more than likely they already did immediately on purchase.

[–] StudioLE@programming.dev 6 points 2 years ago* (last edited 2 years ago)

Yes, included in the 12 month license is the entitlement to that version forever.

12 months of uninterrupted subscription payments qualify you for receiving a perpetual fallback license.

https://sales.jetbrains.com/hc/en-gb/articles/207240845-What-is-perpetual-fallback-license-

Also worth noting that unlike every other subscription service they reward loyalty with large discounts on renewing annually.

[–] StudioLE@programming.dev 6 points 2 years ago

I heard she was running a twitter account that tracked her father's private jet movements

[–] StudioLE@programming.dev 2 points 2 years ago

My subscription expires in two days so this has worked out rather well for me.

[–] StudioLE@programming.dev 5 points 2 years ago

What phrasing are you saying is dishonest? A quick search of proton student discount doesn't even bring up any results from them

[–] StudioLE@programming.dev 14 points 2 years ago (1 children)

My mantra has always been to bring solutions not problems. Applying that to code reviews makes for a far more productive experience.

Rather than just pointing out errors in code help the developer with prompts towards the solution.

Or, if you're too lazy to explain why something shouldn't be done then why should another developer have to act on your criticism?

[–] StudioLE@programming.dev 2 points 2 years ago

I wish this had been my experience. I pushed for so long in my last company for standards to be written, code formatters implemented and objectivity to be brought to reviews but it was always ignored.

Instead I had to endure every employee who claimed seniority (in a non hierarchical company) subjecting their opinion on style in reviews. It came up the point that I dreaded having to work with specific people because they kept triggering my PTSD with their moving target of micro management.

Only afterwards did I truly appreciate how poor a lot of their opinions were. Now one of my first questions when approaching a new project is what standards we're following. If they look at me blank faced that's a pretty solid red flag.

[–] StudioLE@programming.dev 4 points 2 years ago

This was my experience too. At first I found code reviews to be an invaluable resource for improving my code. But I then reached a point where I'd learned everything I could from a particular reviewer.

I'd submit code that met every criteria, but the reviewer would still nit pick on tiny details that were entirely subjectective. It was no longer about the quality of code it became about the reviewer trying to put their mark on my work.

The only solution was to either ignore their nits or adopt the hairy arm technique whereby you include intentional errors for the reviewer to comment on so they feel their time had been valuable and you get away without yours being wasted.

[–] StudioLE@programming.dev 7 points 2 years ago

jQuery was an essential stepping stone back when JS was lacking a ton of features that people take for granted these days.

Sure everything could have been done with Vanilla JS but it was verbose and difficult to follow. jQuery made it possible for any developer to quickly make a page dynamic

[–] StudioLE@programming.dev 30 points 2 years ago* (last edited 2 years ago)

Putting a dead character in a container and then yeeting that container into a chasm will no longer permanently destroy the character - they will now float around as a resurrectable Soul Echo as expected.

QA clearly wasn't good enough if they didn't pick up on such a game breaking bug prior to release

And...

If you dismiss your companion to camp and shove them into a chasm, Withers will now be able to resurrect them... so you can shove them into a chasm again, probably.

Whoever wrote these notes really deserves some credit

view more: ‹ prev next ›