I’m still looking for the glasses to show op is a professional.
I’m still looking for the glasses to show op is a professional.
Ligatures make code way easier to read, especially if you’re using lambdas or a language with different comparison operators than “normal”.
It says 2023, not 24. Commenter typo’d. and the top number is correct. Bottom one is probably custom filled out, not based on actual work history.
Just in case you don’t actually know, it’s Looks Good To Me. It’s very commonly used when software devs review each other’s code.
I got one a while back and it’s fundamentally useless, even with attachments. If you’re actually going to do penetration testing you would be better off getting actual pentest devices. This is just a toy.
Also the difficulty is in the production line and custom swappable components, not the case design.
Last summer. We have a lot for camping. We make sure to have one for each are we go to. I also have charts for nautical navigation.
Nohello.net or whatever the URL is
Gaming desktop, two laptops (one for work, one for personal), phone, a NAS for server stuff.
Take two makes the best coop games
I miss why… he was what everyone really needed, and the industry destroyed him. I haven’t seen anyone like him since.
Just use kagi. Statistically better.
I’m glad he’s doing better
I informed my SecOps team and they reached out to Slack. Slack posted an update:
We’ve released the following response on X/Twitter/LinkedIn:
To clarify, Slack has platform-level machine-learning models for things like channel and emoji recommendations and search results. And yes, customers can exclude their data from helping train those (non-generative) ML models. Customer data belongs to the customer. We do not build or train these models in such a way that they could learn, memorize, or be able to reproduce some part of customer data. Our privacy principles applicable to search, learning, and AI are available here: https://slack.com/trust/data-management/privacy-principles
Slack AI – which is our generative AI experience natively built in Slack – is a separately purchased add-on that uses Large Language Models (LLMs) but does not train those LLMs on customer data. Because Slack AI hosts the models on its own infrastructure, your data remains in your control and exclusively for your organization’s use. It never leaves Slack’s trust boundary and no third parties, including the model vendor, will have access to it. You can read more about how we’ve built Slack AI to be secure and private here: https://slack.engineering/how-we-built-slack-ai-to-be-secure-and-private/
yeah not ideal, but if the actual functionality of that operator hasn’t changed then I wouldn’t expect the version to matter. Same with searching most ruby stuff and getting old results. it hasn’t changed in decades, it ain’t changing now. But I did scroll down and literally every result was from the postgres docs so that’s a marked improvement from the google results.
Because foss is usually not the easiest option. In fact it’s often quite difficult to maintain. So not only creating foss but then hosting your projects on foss is not tenable. Where does the line get drawn? OK you’re running forgejo. Are you running it on infrastructure that you control? You don’t control the DNS, you don’t control the ISP, you don’t control the fiber, you don’t control most of the stack. Putting something on GitHub is really inconsequential if you’re making your project open source since anyone can use it for anything anyway, so who controls the platform doesn’t matter in the slightest.
Kagi ftw.
Reynolds wrap literally has this as a faq on their website because so many people think it.