![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
// I told them I'd do this but only if they gave me time next sprint to fix it - 12-03-1997
// I told them I'd do this but only if they gave me time next sprint to fix it - 12-03-1997
I feel like something like https://www.storj.io/ is on the path to what we would want/need?
There might be some additional requirements for a true CDN to ensure data is closer to where it’s needed and in as many regions as needed though with the right amount of bandwidth. The data gets stored all over the place, but that doesn’t mean its optimal. But they do seem to claim it’s faster on their website…
Edit: For those not wanting to click, TLDR is they use excess storage around the world and make it accessible anywhere, and safe from failures. People with excess storage can join the network if they have enough storage/bandwidth and pass some tests. Their API is S3 compatible.
The best deals you usually only get 2 or 3 toppings as well.
I can make a nice pizza with 3, but 2 often feels lacking.
Ah my bad, you’re right.
Then you’ll probably get shanked if any of the other inmates find out you were sent there for CP.
Have the AI try to recreate existing CP already deemed to have serious value and then have all the prompts/variations leading up to the closest match as part of an exhibit.
Edit: I should add, don’t try this at home, they’ll still probably say it has no value and throw you in jail.
There has been yes, but it doesn’t mean it’s the right ruling law. The law varies on that by jurisdiction as well because it is a murky area.
Edit: in the USA it might not even be illegal unless there was intent to distribute
By the statute’s own terms, the law does not make all fictional child pornography illegal, only that found to be obscene or lacking in serious value. The mere possession of said images is not a violation of the law unless it can be proven that they were transmitted through a common carrier, such as the mail or the Internet, transported across state lines, or of an amount that showed intent to distribute.[
So local AI generating fictional material that is not distributed may be okay federally in the USA.
It’s actually not clear that viewing material leads that person to causing in person abuse
Providing non harmful ways to access the content may lead to less abuse as the content they seek no longer comes from abuse, reducing demand for abusive content.
That being said, this instance isn’t completely fabricated and given its further release is harmful as it it involves a real person and will have emotional impact.
Those times you see an oddly specific and very weird rule and you just know there’s probably a great story around it.
No one cares if you leave a ticket open due to a bug or incomplete feature
Product sure as hell cares if you’re going to ship a bug or incomplete feature.
Never worked at company that wasn’t the case in over 15 years.
Product owns the work they ask us to do. We do their bidding.
And we certainly aren’t allowed to just change the scope of tickets at our own discretion without checking in
Apple won’t like that doomsday event lol
Give it long enough and somehow the person who decided on IPv6 will feel the same as every piece of matter we want to interact with can be networked.
I’m sure many smaller companies had their own internal Y2K moment as they scaled and became a big hit, and realized they used a wrong datatype like int instead of long or something and shit was gonna break by XYZ date if they did nothing heh.
This is my typical experience as well, too many people don’t do a code review of their own PR first.
When I was a junior, I had this coworker who did all my reviews. I was doing my absolute best and wanted to show that I was learning, so I would review all my work before submitting it and think, how would he review and respond to this code.
That just stuck with me and it’s my normal practice now.
I eventually learned that’s not as normal as I thought. I also tend to give better code reviews than others.
Edit: the other thing I do is check in with who will be reviewing my code well before I submit anything someone might think is weird and have a discussion about it before the reveiw. If it’s weird, there might be a better way unless were stuck due to technical debt or something, and doing that early vs at the end usually saves time.
So say we all
I’ve caught problems in code review and had to do this even.
Often it’s reading it and realizing there’s a complicated edge case or they missed something entirely.
Sure we can make a different ticket for that to move this along, but we’re getting product to agree first.
You can say what you want about cutting something like the supercharger network and how that can be bad for Tesla, but that can be managed to some extent. Cutting off internships like this is long term a very bad thing. Companies like this need young talent and this is an amazing way to foster and grow that. This can be devastating to their long term future potential.
The NSA doesn’t know if they want to give their AI unfettered access to the internet and its systems.
Judgement Day is upon us.
“hey I wrote this 6 years ago and it still works but it’s gross … please don’t judge me”
“hey I wrote this 5 years ago and it still works but it’s gross … please don’t judge me”
“hey I wrote this 4 years ago and it still works but it’s gross … please don’t judge me”
“hey I wrote this 3 years ago and it still works but it’s gross … please don’t judge me”
“hey I wrote this 2 years ago and it still works but it’s gross … please don’t judge me”
“hey I wrote this 1 years ago and it still works but it’s gross … please don’t judge me”
“hey I wrote this last month and it still works but it’s gross … please don’t judge me”
“hey I wrote this yesterday and it passed QA but it’s gross … please don’t judge me”
That makes sense ya
It definitely feels great when I get to remove the
//hack abc due to bug in library xyz version 1.4.5, issue tracker says it’s fixed in 1.5.0. - link