The Travel Version of Settlers of Catan Just Got So Much Better

The Travel Version of Settlers of Catan Just Got So Much Better

For players who can’t bear the thought of being away from their favorite board game, there’s a Portable Edition of Settlers of Catan that’s been around for years now. But it comes packed in a flimsy cardboard box full of tiny cards and pieces that are easy to lose. That’s why this new Compact Edition of Settlers of Catan, which folds up on itself for easy transport, is vastly superior in every way.

The Travel Version of Settlers of Catan Just Got So Much Better

You lose the ability to completely customize the game board, because the various hexagonal tiles are grouped into larger modular two-sided pieces. But there’s still plenty of room to mix things up every time you play to keep things new and interesting. There are also slide-out drawers for safely storing the playing pieces and resource cards during transport, and the whole thing folds into a self-contained trapezoid-shaped case that can easily squeeze into a suitcase.

The Travel Version of Settlers of Catan Just Got So Much Better

Available come June for $45, Catan Compact Edition Traveler even seals the tiny dice into a small cup that players can shake to reveal their roll, without the risk of either of them rolling off the game board or table and going missing. [Catan]

The Travel Version of Settlers of Catan Just Got So Much Better


Toyland: We love toys. Join us on Facebook or follow us on Twitter.

via Gizmodo
The Travel Version of Settlers of Catan Just Got So Much Better

Benchmark Yourself as a Programmer with “The Simple Programmer Test”

Benchmark Yourself as a Programmer with "The Simple Programmer Test"

There are lots of ways to get started with coding, and as long as you get over the intermediate-level learning curve, you could be well on your way to a career as a programmer. But how do you know if you’re good enough to find a job in software development? Simple Programmer offers this 12-question checklist.

The questions are roughly based on "the Joel test," Joel Spolsky’s 12 questions organizations can use to find areas they need to work on and programmers use to evaluate a potential employer. (Things like quite working conditions and a bug database.)

If you want to do a quick self-test to evaluate your own skills, though, you can try the "Simple Programmer Test." These questions include things like using source control effectively, solving algorithm-type problems, naming things appropriately, and knowing how to debug effectively. They’re essentially some of the basic skills required of good software developers, and, the site says, if you score eight or above on these points, you should have a pretty easy time getting a job in this field.

If you honestly score no on some of the items, that’s just a sign of an area to work on.

The Joel Test For Programmers (The Simple Programmer Test) | Simple Programmer

Photo by illustir.


via Lifehacker
Benchmark Yourself as a Programmer with “The Simple Programmer Test”

“Missouri Farm Boy”-Turned-DOT-Engineer Invents a Better Snow-Clearing Vehicle

As we saw in the rooftop snow removal post, getting rid of the white stuff provides unique design challenges for individual snow-clearers. And those challenges grow exponentially when spread over the community level. When entire towns and highways are buried under snow, local officials are tasked with an economic problem: How can we remove as much snow as quickly as possible while using the least amount of resources? Every hour of every day that a road remains unplowed, the local economy suffers; yet there are only so many plows, drivers, and fuel to spare, and there may be another storm coming next week, meaning resources have to be carefully managed.

When the storms start to stack up, traditional snowplows start to look like a hopelessly inefficient investment. Consider a local government tasked with clearing a multi-lane highway, and using this typical solution:

You’ve got to pay for all of those trucks, their maintenance, the fuel that goes into them, the wages of the drivers, the time it takes to gas each of those trucks up, et cetera. And having five or ten drivers tied up in one location means there are dozens of other locations left unattended. Plowing the highways isn’t much good if there’s no one left to plow the local roads leading to the highways.

Enter Bob Lannert, an engineer for the Missouri Department of Transportation in the ’90s (and the guy who took those frozen balloon photos). Lannert’s a man with a background unlikely to be duplicated by America’s latest generation: Raised on a farm, Lannert worked his way through engineering school as an ironworker. This gave him an insight into 1) farm machinery, 2) engineering and 3) building things out of metal, and this cocktail of experiences made him the perfect man to solve this problem. Here’s his solution, called the TowPlow:

What you’re looking at is a towed unit hitched to a regular plow. During ordinary travel it rides in a straight line behind the truck—"I want to be able to go through a 10 foot tollbooth," Lannert told Kansas City Public Mediabut when the driver flips a switch, the wheels can be steered to the side at up to a 30-degree angle.

Once the unit is fully deployed, the single driver has effectively increased his clearing width by 250%. This means one man can now do the work of two, with a fuel savings, and your total fleet of drivers can be spread to cover more areas of the community.

The TowPlow carries tanks filled with salt brine (which will not freeze), and these serve as ballast to keep the wheels in place. The contraption can safely be dragged along at 55 miles per hour, and can also be fitted with salt-spraying hoppers to do double duty.

In the ’00s, after experimenting with two lawnmowers on his farm–one pulling the other one behind and slightly to the side of it—Lannert was convinced his concept would work and patented the idea. He then convinced Canadian manufacturer Viking-Cives LTD. to begin producing them, with a classic sales pitch: "During an evening dinner when visiting the Ontario plant," writes trade publication Equipment World, "[Lannert] drew the idea on a table napkin."

“Ninety percent of engineers I talked to said it wouldn’t work because it was too big,” Lannert said. Other naysayers said, “it can’t be stable,” or “it can’t plow in deep snow.”

Despite whatever skepticism Lannert had encountered elsewhere, Viking-Cives bit, releasing the first TowPlow in 2005, and it quickly became a hit. Today the DOTs in Alaska, Indiana, Kansas, Maine, Minnesota, Missouri, North Dakota, Ohio, Pennsylvania, Tennessee, Utah and Wisconsin all use TowPlows; up north, the Canadian provinces of Alberta, New Brunswick, Ontario and Quebec have all added them to their fleets as well.

“Almost everyone who has bought one came back and bought more," says Gerald Simpson, Viking-Cives VP of Sales. "They didn’t park them in the corner and say, ‘Well, it was a novelty, and it was cute, and it was nice, but it doesn’t work for us.’ Almost everyone has bought more."

The units aren’t cheap—we found conflicting sources online indicating they cost anywhere from $67,000 to $100,000—but with states spending millions of dollars on diesel fuel each year to clear snow, the TowPlow is still a no-brainer investment. "TowPlows can pay for themselves the first year in many states," the company claims, and the math adds up: While it increases the fuel consumption of the vehicle towing it by 10-15%, that’s still an 85-90% savings over having two vehicles do the work.

Lannert’s home state of Missouri now has more than 130 TowPlows in their fleet, and found that they do such a good job of clearing the snow that less salt needs to be sprayed on the roads. That also adds up to a savings. "For every ton of salt we don’t use in the winter, that’s a ton of asphalt we can use in the summer," Missouri DOT Maintenance Superintendent Mike Belt told The Missourian, pointing out that the two materials have similar pricing.

As for Lannert himself, he retired from the Missouri DOT in 2007 after putting in 34 years of work. He now runs self-founded civil engineering firm Snow King Technologies, where he continues to tweak the TowPlow’s future iterations, consult with Viking-Cives, and still trains TowPlow drivers personally. And he credits his background, particularly his familiarity with farm equipment, with his success: "[The TowPlow] would not have happened if I had not been a Missouri farm boy who learned that one can no longer compete by using four-row planters."

Here they are in action:


via Core77 Rss Feed
“Missouri Farm Boy”-Turned-DOT-Engineer Invents a Better Snow-Clearing Vehicle

This 25-Year-Old Computer Just Sold for $23,000 on eBay

This 25-Year-Old Computer Just Sold for $23,000 on eBay

The Apple 1 is the most sought after collector piece of computing hardware. It is the Action Comics No. 1 of retro computing. The first appearance of Superman. The one that started it all. But if there was to be a No. 2, it would be this guy—the Commodore 65.

Although it doesn’t have the meteoric sales numbers like the Apple 1, it is almost on par in rarity. Only 50 to 200 Commodore 65 (also known as Commodore 64DX) still exist. This prototype, created in 1990, "was intended to be the last great 8-bit system," according to Hackaday’s Brian Benchoff, who spotted the original eBay listing.

This 25-Year-Old Computer Just Sold for $23,000 on eBay

The C65 start screen

The Commodore 65 in action

The C65 was meant to be backwards compatible with the C64 but also provide Amiga-level features of the time. The project began in late 1990 but was soon canceled. When Commodore was liquidated years later, some C65 computers were sold to the public, mostly likely the same machines circulating on auction websites today.

You can read more about this tech relic from this dedicated page (which looks like it’s as old as the computer itself). [Hackday]

via Gizmodo
This 25-Year-Old Computer Just Sold for $23,000 on eBay

Instantly Flatten a Directory in OS X with a Terminal Command

Instantly Flatten a Directory in OS X with a Terminal Command

Sometimes we all go a little too nuts on making folders inside of folders and you just need to flatten the whole thing down to one. OS X Daily shows off a handy Terminal command for just that.

When you have directories inside of other directories, you end up losing track of files pretty quickly. To smash the whole thing down into one directory, a simple Terminal command is all you need. In this example, TargetDirectory is the subdirectory you want to move the contents from:

find TargetDirectory/ -mindepth 2 -type f -exec mv -i '{}' TargetDirectory/ ';'

With that, all the files located in TargetDirectory will be moved up into the higher directory. Head over to OS X Daily for a few more examples of how it works.

Flatten a Nested Directory & File Hierarchy from Command Line of OS X | OS X Daily


via Lifehacker
Instantly Flatten a Directory in OS X with a Terminal Command

Explore This Rare Gallery of Hyper Detailed Star Wars Models

starWarsModel_1The site Slightly Warped Curiosities has posted this wonderful, rare gallery of close-up photos of the Industrial Light & Magic spaceship models used in the first Star Wars trilogy. Anyone who scratch-builds models knows the importance of “grebble” — that’s the baroque surface detail–usually cool-looking bits “kit-bashed” from other models–added to […]

Read more on MAKE


via Make:
Explore This Rare Gallery of Hyper Detailed Star Wars Models

SilencerCo Now Sells NFA Trusts for $129

unnamedSilencerCo is now selling the creation of NFA Trusts for just $129. A trust allows all trustees (which could be family members) to use NFA items owned by the trust. It also means that trust-held NFA items don’t need to be transferred to an heir after the owners death, which saves time. SilencerCo says … A properly-prepared […]

Read More …

The post SilencerCo Now Sells NFA Trusts for $129 appeared first on The Firearm Blog.


via The Firearm Blog
SilencerCo Now Sells NFA Trusts for $129

MySQL Character encoding – part 1

Breaking and unbreaking your data
Recently at FOSDEM, Maciej presented “Breaking and unbreaking your data”, a presentation about the potential problems you can incur regarding character encoding whilst working with MySQL. In short, there are a myriad of places where character encoding can be controlled, which gives ample opportunity for the system to break and for text to become unrecoverable.
The slides from the presentation are available on slideshare.
Character Encoding – MySQL DevRoom – FOSDEM 2015 from mushupl Since slides don’t tell the whole story, we decided to create a series of blog posts to demonstrate how easy it is to go wrong, how to fix some of the issues and how to avoid such issues in the future.
What is character encoding?
The encoding is the binary representation of glyphs, where each character can be represented by 1 or more bytes. Popular schemes include ASCII and Unicode, and can include language specific character sets such as Latin US, Latin1, Latin2 which are commonly used in America and Europe and EUC-KR or GB18030 which support language characters with an Asian origin. Each character can be associated by several different codes, and one code may correspond to several different characters, depending on the encoding scheme used.
Where do you set character sets in MySQL?
Here is the core of the problem, the character encoding can be controlled from the application, database or even on a per table or column basis. Together with a set of rules regarding inheritance, it is easy to have one layer of the system configured for one character set whilst the actual data being introduced is using a different character set.
In MySQL the following area, the following settings can all affect the character encoding used.
Session settings
character_set_server
character_set_client
character_set_connection
character_set_database
character_set_result
Schema level defaults
Table level defaults
Column charsets
Character encoding in MySQL.
As Maciej pointed out in the presentation, where MySQL is concerned we are all born Swedish, as MySQL starts configured for the Latin1 character set and collation set to latin1_swedish_ci. This is even the case in MySQL 5.7, meaning by default your system expects only characters in the latin1 set and will when comparing characters it will assume the Swedish language is being used.
Lets look at how this manifests itself in a new application, where server, client and table are set to the default latin1.

mysql> SELECT @@global.character_set_server, @@session.character_set_client;
+——————————-+——————————–+
| @@global.character_set_server | @@session.character_set_client |
+——————————-+——————————–+
| latin1 | latin1 |
+——————————-+——————————–+
1 row in set (0.00 sec)
mysql> CREATE SCHEMA fosdem;
Query OK, 1 row affected (0.00 sec)
mysql> USE fosdem;
mysql> CREATE TABLE locations (city VARCHAR(30) NOT NULL); Query OK, 0 rows affected (0.15 sec);
mysql> SHOW CREATE TABLE locations\G
*************************** 1. row ***************************
Table: locations
Create Table: CREATE TABLE `locations` (
`city` varchar(30) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 1 row in set (0.00 sec)
So what happens when you try to save some data that is not latin1 encoded.
 
The city of Tokyo is displayed.
The application returned and rendered the new city correctly, however inside the database there is some confusion.
mysql> SET NAMES utf8;
Query OK, 0 rows affected (0.00 sec)
mysql> select * from locations;
+——————–+
| city |
+——————–+
| Berlin |
| KrakÃ3w |
| 東äo¬éƒ1⁄2 |
+——————–+
3 rows in set (0.00 sec)
The data being saved was UTF8 encoded, however if an application attempts to query the database as UTF8 it receives garbage. Instead the application must ask for Latin1 to receive the original data.
mysql> SET NAMES latin1;
Query OK, 0 rows affected (0.00 sec)
mysql> select
+———–+
| city |
+———–+
| Berlin |
| Kraków |
| 東京都 |
+———–+
3 rows in set
* from locations;
(0.00 sec)
The new city was saved and from the application the result looked correct, however what is happening here is that the connection to the database has saved the binary data without any manipulation. Hence it returned the same data, and the browser was able to do the right thing and display it correctly, as did the terminal which was set to UTF8. Inside the database though, it is not able to understand the data in the correct context.
In the next blog post we will look at how to correctly configure character sets, as well as demonstrating some of the problems we have encountered in production systems and how we fixed those.
via Planet MySQL
MySQL Character encoding – part 1