datasink

https://www.youtube.com/watch?v=XEM5qz__HOU (Palantir AIP | Defense and Military)

I hadn't really thought about it until now, but these pharmacists did not directly work with each other, so it must have been obvious that phenylephrine was ineffective.

From what I've heard, the problems they saw were with things like the cost of electricity consumed when doing multi-unit charging at schools and difficulty in integrating OLPC devices into teacher-driven curriculums.

In Cambodia at the moment, it seems like inexpensive Android devices are starting to deliver on some of the promises of the OLPC program. They're rugged, energy efficient, simple for children to use, and have a large variety of educational apps and material available (though fewer are available in Khmer). A family owns it, so issues like theft and damage are their responsibility. I vacationed in Cambodia last year, and was amazed to see how many smart phones were in common use, even in poorer areas.

I think it's pretty unlikely, even if he did take various measures to hide, that he'd be able to if influential foreign governments were putting pressure on the Cambodian government to find him. Cambodia is a pretty tiny country.

I've also seen a good number of developers that would never touch Adderall, but drink a horrendous number of free energy drinks throughout the day, for much the same reasons.

The US government doesn't care much about the chemicals that might be reasonably used for chemistry experiments. The DEA watchlist is pretty specific and I don't believe the DHS/FBI/ATF are going after people buying small quantities of chemicals that have legitimate uses.

This excerpted anecdote indicates it was mainly a leadership gesture to rally the troops. Still pretty cool that he'd bother, though.

A similar script, but with an 'addsite whatever.com' command.

I think in most cases criminals are suitably stupid enough to make law enforcement's job much easier. Like, for example, busting someone who is trying to break into a lab with a security system, and then finding a meth lab in their mobile home.

Getting caught while stealing glassware from a lab is a much larger risk than having someone at a for-profit lab supply company play junior detective with your glassware order. This might not be entirely obvious while high on crack, though.

My takeaway from this: if you care about impeccable quality, it's a constant fight to get it and keep it. No one will care about your product as much as you do.

Some things I found useful for these high-value offset print jobs:

1. Print out a hard proof (at full size obviously), and have multiple people review its accuracy.

2. Provide your printer with both a PDF/X file and your Indesign file. Use Indesign. Ask your printer if they have a preference for the PDF/X settings.

3. Provide all of the above to your print house.

4. Request, at the very least, an e-proof from your printer. This is generated after they push it through their processing workflow. If it looks good, your only other concern would be press calibration.

5. If it makes financial sense, schedule a press check. I believe we paid $100/hour for ours, but they would not usually take more than an hour. I'd usually ask for adjustments if they were needed, then pluck off a print that looked good and sign it. I'd take an identical copy for myself. They'd then use this to compare press output with during the printing job. If any part of the job came out like crap, I could use my copy to show how off it was and get a refund or credit on my next job.

To answer your question specifically: it would be smart to use Twig by default, rather than developing your own custom Fuel template engine, because you would need to spend a significant amount of time to get something with the same feature-set, build quality and documentation coverage. Would this time not be better spent elsewhere?

As a pretty content Fuel user, I should also mention that your tone doesn't benefit the project.

"Tons of problems and weaknesses" is largely untrue at this point. Many of the problems that were traditionally pointed to were corrected in 5 and 5.3. There is no interest in breaking backwards compatibility, so the built-in function parameter order inconsistencies are still valid. Most frameworks work around this issue with an OOP wrapper for array and string operations.

It is difficult to find good dev-power for PHP that's cheap. I've tried. You can find many people who have a basic level of PHP knowledge and refer to web apps as "scripts". Finding people who have an understanding of OOP and modern development techniques is much harder and more expensive.

Here's why I program web apps in PHP: it works and I know it well. If I need a library for something web related, I can assume it will be available as open-source. I don't have concerns that I can make a PHP application scale if I need to. When features don't make sense to implement in PHP, I'll snap them off and implement them in the most appropriate language in the background. Most of the heavy-lifting for web applications typically happens in the background.