@Azure's OpenAI has become unusable lately due to their content moderation policy.
Responses often takes more than 10 sec to even start streaming & refuses to process technical terms like "Discovering Child Elements" due to "triggering Azure OpenAI's content management policy"
I can't believe how cumbersome creating a new price in @stripe is.
If I want to change the price or add a new currency, I have to manually create a new price, copy over every single value and currency by hand and hope I didn't accidentally make a typo.
One lesson from implementing @stripe -- A significant weakness is the inability to version products/prices. Juggling metadata, lookup keys, and active vs. archived prices adds complexity.
Remember back when we all read Clean Code and then to do one thing we wrote 25 small functions across several files instead of one 20-line function that you could look at and say "I know exactly what this function is doing"
Absolutely zero offense to the author, but how can anyone open this test and even begin to understand what's going on here?
It succeeds – what exactly does it verify? It fails – what exactly is broken?
That's the kind of code that mocking frameworks inevitably bring you toward.
10x engineers blah blah blah who cares. The engineers that impress me the most are the ones that fearlessly dive into code, domains they know absolutely nothing about and end up producing amazing work in a short amount of time anyways. Truly awe-inspiring every time I see it.
Recursive sum/union types with exhaustive pattern matching is by far and away the highest leverage programming language feature post lambdas, I wish every language would adopt
Played MS Flight Simulator in VR for the first time and was completely lost with even the basic plane setup.
Instead of watching YouTube tutorials, I opened ChatGPT's voice conversation feature on my phone and told it to act as my flight instructor. (1/3)
It explained to me *every single step* I needed to know about getting the plane off the ground and setting up the autopilot in the air, while patiently answering all my questions I had about aviation. (2/3)
A common mistake: "Let's abstract this in case we want to replace it later."
Examples:
🚫 "Let's abstract React in case we switch JS frameworks."
🚫 "Let's abstract Tailwind in case we switch CSS approaches."
🚫 "Let's abstract Mongo in case we switch Databases".
This is typically a waste of time, and often hinders current use too.
Why? Because to effectively abstract something, we need to know the API we're abstracting.
But we have no idea what a new technology's API will be. Thus, we have no idea whether our abstraction will work with the new technology.
In summary, abstraction can be useful. But avoid abstracting merely to support changing to some unknown future technology.
Had to refund and cancel 240 customers called Jake Smith from Philippines with $7,000 in card testing payments
No idea why Stripe doesn’t catch these
They even passed my Cloudflare CAPTCHA?!
Had to block 🇵🇭 PH payments now sorry
I am looking for an addition to our frontend team @getmimo. If you value autonomy, a great team and you like to work on a meaningful product, just reach out!
https://t.co/9bUyAGKZqS