// This function calculates applicable discounts given a customer's loyalts status
// STOP BEFORE SEASON 8 DEXTER PLEASE
fun calculateDiscountRate(loyalty: LoyaltyStatus): Set<Discount> {
...
// This function calculates applicable discounts given a customer's loyalts status
// STOP BEFORE SEASON 8 DEXTER PLEASE
fun calculateDiscountRate(loyalty: LoyaltyStatus): Set<Discount> {
...
It’s too late, we can’t contain it
Outlook
Outlook (New)
Outlook (Newer)
Outlook (Newest)
Outlook (Newest final)
Outlook (Newest final V2)
That’s right! It goes in the square hole
I don’t know how to React to this.
Write down any NaN advantages of JavaScript
Yes I believe they dragged it to the wastebasket
I believe the idea is to potentially induce a brief nasal snort possibly accompanied by a slight upward curling of the lips in those casually scrolling by. In other words, it’s a joke, being posted on a joke community.
Yeah it is but the doc can write you a script for that.
Do you have CSS as well? I heard if you get one you probably have the other.
Peter screwed up again, dammit. We can’t afford to have any more outages or we’ll miss all our SLAs!
I think it’s pretty useful, be interested to hear your hangups with it though because it’s definitely not perfect.
If something goes wrong and I have a stack trace, that plus the type of exception will almost always be enough for me to figure out what’s wrong at least as a starting point. I’ve worked mostly with JVM languages in my career though so maybe I just don’t know how bad it actually is.
This seems like a generic type of problem that could happen to anyone. Hopefully we can learn from this and avoid appending it to our already large grid of problems.
Then a year or two later you quit/get fired/move to a new team and that code is underpinning a business critical task. Everyone responsible for the code is scared to do any major refactoring because of how important it is but it seems to be working ok. Hopefully they’ll have time for a big refactor next quarter when they can afford to take some time and manage the associated risk.
Seems legit to me typeof 🎈=== "spaceship"
is probably true
in JavaScript after all
I don’t know if this is the proper definition but I think of boilerplate as the code that’s not directly related to business logic. An example I can think of in Java that’s a lot nicer in Kotlin is setting all the instance variables in the constructor.
The names and types of the variables are important and useful for understanding the business logic but the actual constructor definition doesn’t tell you anything if it’s just assigning the constructor parameters.
In case of
Git commit
Git push origin main --force
Fire
Fortunately it doesn’t seem too deep, it’s really difficult to learn under pressure
Sounds like you need to add some sleep statements somewhere in your deployment scripts if you want to deploy in 10 seconds