Imaginable used in a sentence

Imaginable in a sentence as an adjective

So, once you put on that uniform you have to keep your mouth shut even if you witness the worst atrocities imaginable. Is that your opinion?

> So, once you put on that uniform you have to keep your mouth shut even if you witness the worst atrocities imaginable. Absolutely not.

Every day, in every situation imaginable, there are hundreds of ways to meet people. There really are.

Together with SAP, Microsoft has the most complete enterprise stack imaginable. All of a sudden even Windows Phone would have a place in this world as a BlackBerry successor.

Not only are you suffering from the worst kind of emotional pain and loneliness imaginable, but you're being told that you're a fool for it, and that you're a failure or a weakling for not being able to snap out of it. That's dangerous.

Not the most inhumane thing imaginable but still pretty stomach churning to listen to his screams on the scanner. Those brave warriors sure had their "fun" with a semi-conscious unarmed drunk guy that day.

Fanboys on either side of the aisle love to pat themselves on the back and reaffirm--almost daily--that yes, they did buy the best product imaginable. It's the same reason Gruber makes half a million a year writing snarky one liners.

I'm neither rich, nor good-looking, nor in any imaginable way socially interesting. Seriously, it's stunningly stupid, and I can't for the life of me understand what powers this process.

There is no imaginable practical consequence from this besides expressing unhappiness. That doesn't mean the gesture is meaningless.

Of all the businesses you can try to import to bring more "desirable" traffic to the area, you had to pick the one that caters all meals internally and has every imaginable perk already in-house? This is supposed to bring new businesses to the area?

Worse kinds of evil are imaginable, like not telling users anywhere that data is being or collected or making it hard for users to turn the collection of data off.

They built better tools, drilled security into every new hire all the way to the execs, made it a part of every engineering and product process imaginable. Happy that is finally being acknowledged on the outside.

Imagine how the developer community would fare in a lottery system where every API-related claim imaginable were tossed to a jury with prospects for a ****-shoot outcome. If that is a horrific thought, then you have one more thing for which to thank Judge Alsup.

He could have had fetal alcohol syndrome, he could have been a crack baby, he could have been broken in many imaginable ways. Instead, they took this baby, they stood by it even when the 911 operator didn't believe their story, they made sure it was looked after, and when asked they agreed to raise it without hesitation.

The company lawyers will work to ensure that all emphasis is placed on the worst legal risks imaginable, even if there is another side of the story. This may not be as true in Forture 1000 companies where the positions are more entrenched, but it is true in startups and is therefore ****** for founders who get caught up in such a mess.

Edit #2: If my experience with the Japanese Culture is in any way representative employing more men in the military will be the worst thing imaginable. The country has a deficit of 180% /GDP and every person in the army is one person less doing productive work to keep country afloat.

*People who say research costs billions, not millions have been suckered by the most pernicious line of ******** imaginable. The "billions" figure does not represent actual R&D costs, which, in a shocking number of cases, represent single-digit percentages of pharmaceutical company budgets.

Then notice how the best outcome imaginable is a compromise. A scenario where you simply get what you want is not even on the table, here, even though it's entirely possible that getting what you want in this case is the best outcome for everyone involved, and at the very least is probably achievable and reasonable.

Keep multiple backups of everything important" is good advice for a user, but "Keep user files safe when the user thinks they are safe" is the most essential advice imaginable for the CEO of an online backup service.

I experienced every data hygiene issue imaginable: from ntpd being broken, local time/UTC inconsistencies, switch firmware acting up, all the way to human errors in the ETL process. Building a reliable data pipeline has so many moving parts that I am fairly pessimistic about any one-stop solution.

Git is a powerful, general tool that lends itself to just about any workflow imaginable and, because of its adaptability, different teams will naturally converge on different Git workflows as "right." These teams, however, have a hard time imagining and thus accounting for the conditions and preferences of other teams, and end up advocating for their workflows as the best workflow.

Imagine scaling up Hacker News so that every member is allowed to post to the top of the front page, and posts are allowed to be on any topic imaginable, and the average comment is going to be at least as knowledgeable and thoughtful as it is here -- in fact, the comments are expected to be good enough that they won't be sorted or threaded, and it will be more or less a faux pas to comment without reading all the comments that came before yours. It'll also be a faux pas to drive away people with contradicting ideas.

If you want to offer alternative interpretations of the data, or point out specific methodological flaws, or whatever, by all means do so - but now you're just saying 'meh I don't like this guy's ideas, he must be a shill, but I guess we'll never know because nobody can know these things anyway' - the most toxic nihilistic and intellectually dishonest 'reasoning' imaginable.