429 karma · joined December 11, 2013
"We believe developers and users should have the flexibility to use our services as they see fit, so long as they comply with our usage policies. We're exploring whether we can responsibly provide the ability to generate NSFW content in age-appropriate contexts through the API and ChatGPT. We look forward to better understanding user and societal expectations of model behavior in this area."
Yes. It will be a bit more work on the pedalling front vs a dedicated gravel bike, but I doubt you will encounter any bike snobbery. I have gravel trails near where I live, and you see all kinds of bikes tackling them.
> "We are doing a prototype on our new mapping product, we need to write a one-off script to pull in some map data."
... is just that - a one off script. And it can prove to be a lot quicker to write a one-off script than getting involved with an ETL framework. I am not arguing against ETL Frameworks (Airbyte etc). Just that over-engineering carries its own costs, just like under-engineering does.
I took the approach that in your 20s you are still forming, still growing, still malleable. The experiences you have in your 20s will have a disproportionate effect on the kind of person you end up being. Therefore, you have to think about what environment, what experiences you want to foster that growth in. I would suggest optimizing for variety and new experiences is a better idea that working 80 hours weeks throughout your 20s. In your 20s, don't just work hard, work hard at becoming the person you want to be.
(Actually, the 6th ball - the "powerball" is picked from a set of 20 just to complicate things)
I find both have valid points and there isn't really a compromise. Whichever approach is taken you end up with half the team feeling not listened to and disenfranchised.
I have found few things to be more divisive than the ORM vs No ORM debate and I am not sure what the answer is.