As a trip-it free tier user, it’s not clear to me why this is a better choice. Is the value add purely the voting?
119 karma · joined August 10, 2019
It's called "According to Need"
Thanks for the idea!
But really, it doesn't actually add any additional functionality, however, they add a huge amount of attack potential by bad actors or ads/privacy tracking.
I generally run with JS off, and enable it on case by case basis. I find my life isn't impacted that much and I feel safer knowing my browser isn't doing a ton of behind the scene code.
When did he leave? And what is he doing now?
Hardware raid controllers with Battery Backup Units was really popular starting in the mid 90’s until maybe mid 2010’s? Software caught up in a lot of features and batteries failed often and required a lot more maintenance. Super caps were to replace the batteries but I think SSDs and software negated a ton of the value add. You can still buy them but they’re pretty rare to see in the wild.
That’s what I do currently and it works just fine. I’m unclear if there’s something this does extra that I’m overlooking?
Honestly I think this will end up proving to be a misstep akin to reader.
100 megabytes per second for 2 months is 518.4 TB.
the 850 evo 1 TB has a warranty of 5 years or 150 terabytes written, so Norton has totally destroyed the warranty. And there's a decent shot that the drive will fail soon...
Restaurant vs Cafeteria
Espresso vs Drip
Cafe vs Starbucks
Backyard BBQ vs McDonalds
I actually think that garden vs farm is a good choice. The others are a bit funny to me :)
Another thing to consider is international cultures. There’s been concern around calling servers cattle and saying to just shoot them in the head during work meetings. Some cultures may have issues with that.
They wanted my real address and ended up without it.
This is The same argument against DRM. It hurts the legit folks and didn’t impact the pirates.
Don’t build barriers for the people you want.
1. Split up ingredients into more parts.
2 tbsp ground black pepper is actually: Quantity: 2 tbsp Ingredient: Black Pepper Preparation: Ground
2 finely chopped scallions, just the white parts Quantity: 2 Ingredient: Scallions Preparation: Finely Chopped Note: Just the white parts
Often you'll have apps (like plan to eat) that adds the preparation to the ingredient and makes shopping lists much harder to manage
2. Ingredient replacements. Often you'll see recipes calling for one ingredient and then has "You can replace this with x and y". It would be extremely nice to have this programmatically available. I know if I can't find scallions, I can replace it with garlic and onions.
3. Variants. Often I have the same core recipe in my recipe book with just different variants. Meringue cookies with different flavors. 90% of the recipe is all the same, but it's duplicated a dozen times for a dozen specific flavor add-ins. It would be extremely nice to have this somehow programatically available, so I can have the base recipe and all the variants with a reused core :)
These are my options, some shared by others in the threads here, some opposite.
> It would lock the low-level features that allowed you to make calls, use Wifi, or even post pictures on Instagram/Facebook (the horror!) until you paid up. ... > Except for the poor sod in Peru who couldn't make phone calls or post duck-face pictures to Instagram, but no one asked him.
Both of these quotes seems like you don't quite understand the impact on your end users, or just don't care. Neither are good options as you grow your career.
> Our own internal tool worked well (I would like to say it was all due to me, which would be an arrogant thing to say, but also 100% true, so I will say it: It was all or mostly due to me).
Your internal tool, which you are taking complete credit for, is what didn't have protections in place that ended up harming users. Also, it comes across as bragging or something. People that are too obsessed about credit usually are not ones I'd like to work with. Team efforts are hard to define and split up and people that over index on that usually are just bad team members.
> But one mobile phone manufacturer (that I will call the K-Pop Phone Manufacturing Company), based in Korea (yes, that one)
Say it or don't. These games where you can act all cheeky about how you didn't 'actually' say it is just juvenile IMHO.
> Because of time pressures, there was no time (or political will) to check the script was well written. As soon as I banged it out, it was live. And I mean literally, 10 seconds after I pressed save, the script was running on live production servers.
This is beyond just the org's failure. As engineers, we're responsible for what happens on our watch. We hold the line and try to enforce engineering practices, not shrug and yolo and then blame the org.
> I could have tested it better, but that would have meant working late into the night. No thanks. I had already worked a few late nights/weekends and I was done.
This comes across as again, you don't actually care at all. Not a hiring quality IMHO
> My colleague was helping me, so we got it all done in about an hour. By 18:30, we had unlocked all phones.
Oh no! You worked an entire hour between 5:30 pm and 6:30 pm! The horror! Most people work much much longer hours, later into the evening or night when things fail. The difference is they don't complain about it and care.
> A project manager confirmed it, and I took a breath of relief and quickly logged off before more fuckups could be found.
Great! You fixed it, but rather then trying to verify you fixed everything, you logged off at 6:30 and screw anyone else effected. Not a great look.
> The Lessons we learnt (or more likely, didn't learn)
If you didn't learn the lessons, why are you writing about it? Just as a war story? Or do you think this comes across as a positive for your career?
> The lesson here is: Do some f'king checks before you lock someone's phone, but I don't know if that lesson applied to us or K-pop (most likely, both of us).
You know. You're in control of what you can do, so you do what you can to prevent issues from happening under your watch.
> This is not just good QA, but good security as well. But bah! None of that silliness for us, thanks.
Again, you come across as uncaring. Why are you working in this industry?
> We assumed that because our own software checked for this sort of thing, that the K-pop phone's software would do as well.
Great. Your software failed. Don't blame downstream if you can't even get your first layer correct.
> Everyone pretended it was an honest mistake.
It was an honest mistake. The difference is if you learn and grow, or if you just shrug and make the mistakes over and over again.
Honestly, this is just my two cents. Take it all with grains of salt, and ignore as you wish. I don't intend to be personally attacking you or any of the sort. Just expressing where my mind is reading it.
If I was you, I'd take this down and seriously consider if engineering is the right career path for you. It doesn't seem like you actually enjoy it or care about it and just working for the easy money doesn't lead to a fulfilled life at the end. And living a fulfilled, happy life, is the most important thing after all.
Best of luck in the future.