[syndicated profile] winsupersite_feed

read more

[syndicated profile] icanhascheezburger_feed
cute gender reveal photo shoot for a new puppy

Kennedy Sartwell and Jake Terry of Warrensburg, Missouri, are an adorable loving couple who recently adopted a precious puppy named Raven. Excited about the new arrival, the couple decided to skip the regular posting on facebook or sending photos to a group chat and to do something bigger to announce Raven to the world. The couple recruited a professional photographer, Kennedy's mother, Cristy Sartwell of Infinite Smile Photography, to shoot a sex reveal photo series. The results are so cute! Via: People



Submitted by:

[syndicated profile] winsupersite_feed
Alphabet Inc.’s Nest, seeking to push its devices into more aspects of people’s homes, introduced a full suite of security products, including a digital-video enabled doorbell, an outdoor camera with a loudspeaker and an alarm system.

read more

[syndicated profile] icanhascheezburger_feed
cats that love to fly

Mausi & Miseli are two adorable and fearless cats from Switzerland who love to fly. Their Instagram Account is taking off and reaching new heights (Over 20K loyal fans worldwide). Mausi is three years old (born 16th of May 2014) and Miseli is almost a half year old (born March 28th, 2017). Mausi is actually the proud mom of Miseli! Their owner, Sara, told the Purrington Post: "As the kittens were super playful and always jumped to get their toys, I just wanted to try and see how it looked in a photo. As their poses were so funny during their flight, I started to take more and more. I took my first photo of a flying kitty back in July of 2015. A year later, I had uploaded around five more flying kitty photos on Instagram. This year I've already uploaded more than 30 flying kitten photos and I think every one of them is super unique." Miseli is a professional jumper and Mausi just jumped once in a while during a photo shoot. Via: The Purrington Post





Submitted by:

Tagged: Switzerland , Cats , flying
Sep. 20th, 2017 06:51 pm

News Post: My Thing

[syndicated profile] pennyarcade_feed
Tycho: I’m still thinking about my SCA shit up at last weekend’s Banner War, partly because I got sick there so I’ve had a lot of time to lie completely motionless except for wracking coughs and the occasional turn, as meat is turned on a grill, to let the mucus collect in the other lobe of my sinuses. Here is the comic which recounts a vital portion of the experience.  I always wonder how I’d fare in another context; statistically speaking, “dead at another’s hand in the service of someone I don’t know” is probably the correct assessment. …
[syndicated profile] winsupersite_feed
The technology first developed in the 1960s has been mostly relegated to the realm of government agencies and high-security firms. But if it follows the same path as Apple’s previous rollouts, it’s just a matter of time before the technology starts popping up in homes, stores and on other phones.

read more

[syndicated profile] winsupersite_feed
An issue cropped up in Windows 10 Redstone 3 Build 16288 that caused some Surface Pro 3 devices to become unbootable but alongside of a new build release Microsoft is providing those users a work around until the fix catches up in a future RS3 build.

read more

Sep. 20th, 2017 12:42 pm

The Big Idea: Fran Wilde

[syndicated profile] scalziwhatever_feed

Posted by John Scalzi

Today, award-winning author Fran Wilde has a shocking confession to make! About something she said! Here! And yes, it involves her new novel, Horizon. What will this confession be? Will there be regret involved? Are you prepared for what happens next?!?

FRAN WILDE:

Dear readers of John Scalzi’s blog, for the past three years, I’ve been keeping secrets.

I’m not sorry.

Trilogies are a delicate thing. They are a community of books unto themselves. They inform and support one another; their themes and actions ripple and impact one another. They have their own set of rules. Among them: Write down the main character’s eye color or favorite food so you don’t forget it. You’ll regret using that hard-to-spell naming convention by the middle of your second book. Destroy something in book one, you’re not going to magically have it to rely on in book three — at least not without some major effort. Everything gathers — each choice, each voice.

Trilogies are, by intent, more than the sum of their parts.

And, when brought together, a trilogy’s largest ideas sometimes appear in the gathered shadows of what seemed like big ideas at the time.

In Updraft, book one of the Bone Universe trilogy, what began to crumble was the system that upheld the community of the bone towers. It didn’t look like it then. So I didn’t tell you when I wrote my first Big Idea.

Instead, the first time I visited this blog, I wrote: “At its heart, Updraft is about speaking and being heard and — in turn — about hearing others…”

That was true – especially in the ways Updraft explored song as memory and singing and voice. But it was also kind of a fib. I knew where the series was headed, and voice was only the tip of the spear.

I planned to return here a year later to write about leadership, and I did — and, I wrote about demagoguery too, and abut having a book come out during a charged political season. That was September 2016, Cloudbound, the second book in the series was just out, and wow, that post seems somewhat innocent and naive now. But not any less important.

Again, saying the big idea in Cloudbound was leadership was true on its face, but it was also a an act of omission. And again, singing came into play — in that songs in Cloudbound were being adjusted and changed, as were messages between leaders.

With Horizon, I’m going to lay it all out there for you. Horizon is about community.

Structurally, Horizon is narrated by several different first person voices — including Kirit, Nat, and Macal, a magister and the brother of a missing Singer. These three voices come from different places in the Bone Universe’s geography, and they weave together to form a greater picture of the world, and its threats. A fourth voice appears only through a song — a new song — that is written during the course of Horizon, primarily by one character but with the help of their community. That song is the thread that ties the voices together, and, one hopes, the new community as well.

And, like Horizon, for me, the big idea for the Bone Universe series is also community. How to defend one, how to lead one, how to salvage as much as you can of one and move forward towards rebuilding it.

In my defense, I did leave some clues along the way. I shifted narrators between Updraft and Cloudbound in order to broaden the point of view and reveal more about the lead characters and the world, both between the books (how Nat and Kirit are seen each by the other vs. how they see themselves), and within them. I shared with readers the history of the bone towers and how that community, and the towers themselves, formed. I showed you the community’s [something] – that their means of keeping records and remembering was based on systems that could be used to both control messages and redefine them. I made the names of older laws and towers much more complicated to pronounce (and, yes, spell SIGH), versus the simpler names for newer things. This community had come together, then grown into something new.

The evolution of singing in the Bone Universe is, much like the idea of community, something that can be seen in pieces, but that resolves more when looked at from the perspective of all three books together.

Remember that solo voice — Kirit’s — singing quite badly that first book? In the second book, Nat’s voice joins Kirit’s — a solo, again, but because we can still hear Kirit, and because we know her, it becomes a kind of duet. In the third book, three voices present separate parts of the story, and when they all come together, that forms a connected whole.

When you listen to a group of people sing, sometimes one voice stands out, then another. Then, when multiple voices join in for the chorus, the sound becomes a different kind of voice. One with additional depth and resonance.

That’s the voice of a community. That drawing together of a group into something that is more than the sum of its parts. It is an opportunity, a way forward, out of a crumbling system and into something new and better.  

That’s the big idea.

—-

Horizon: Amazon|Barnes & Noble|Indiebound|Powell’s

Read an excerpt. Visit the author’s site. Follow her on Twitter.


Sep. 20th, 2017 10:30 am

CodeSOD: A Dumbain Specific Language

[syndicated profile] the_daily_wtf_feed

Posted by Remy Porter

I’ve had to write a few domain-specific-languages in the past. As per Remy’s Law of Requirements Gathering, it’s been mostly because the users needed an Excel-like formula language. The danger of DSLs, of course, is that they’re often YAGNI in the extreme, or at least a sign that you don’t really understand your problem.

XML, coupled with schemas, is a tool for building data-focused DSLs. If you have some complex structure, you can convert each of its features into an XML attribute. For example, if you had a grammar that looked something like this:

The Source specification obeys the following syntax

source = ( Feature1+Feature2+... ":" ) ? steps

Feature1 = "local" | "global"

Feature2 ="real" | "virtual" | "ComponentType.all"

Feature3 ="self" | "ancestors" | "descendants" | "Hierarchy.all"

Feature4 = "first" | "last" | "DayAllocation.all"

If features are specified, the order of features as given above has strictly to be followed.

steps = oneOrMoreNameSteps | zeroOrMoreNameSteps | componentSteps

oneOrMoreNameSteps = nameStep ( "." nameStep ) *

zeroOrMoreNameSteps = ( nameStep "." ) *

nameStep = "#" name

name is a string of characters from "A"-"Z", "a"-"z", "0"-"9", "-" and "_". No umlauts allowed, one character is minimum.

componentSteps is a list of valid values, see below.

Valid 'componentSteps' are:

- GlobalValue
- Product
- Product.Brand
- Product.Accommodation
- Product.Accommodation.SellingAccom
- Product.Accommodation.SellingAccom.Board
- Product.Accommodation.SellingAccom.Unit
- Product.Accommodation.SellingAccom.Unit.SellingUnit
- Product.OnewayFlight
- Product.OnewayFlight.BookingClass
- Product.ReturnFlight
- Product.ReturnFlight.BookingClass
- Product.ReturnFlight.Inbound
- Product.ReturnFlight.Outbound
- Product.Addon
- Product.Addon.Service
- Product.Addon.ServiceFeature

In addition to that all subsequent steps from the paths above are permitted, that is 'Board', 
'Accommodation.SellingAccom' or 'SellingAccom.Unit.SellingUnit'.
'Accommodation.Unit' in the contrary is not permitted, as here some intermediate steps are missing.

You could turn that grammar into an XML document by converting syntax elements to attributes and elements. You could do that, but Stella’s predecessor did not do that. That of course, would have been work, and they may have had to put some thought on how to relate their homebrew grammar to XSD rules, so instead they created an XML schema rule for SourceAttributeType that verifies that the data in the field is valid according to the grammar… using regular expressions. 1,310 characters of regular expressions.

<xs:simpleType>
    <xs:restriction base="xs:string">
            <xs:pattern value="(((Scope.)?(global|local|current)\+?)?((((ComponentType.)?
(real|virtual))|ComponentType.all)\+?)?((((Hierarchy.)?(self|ancestors|descendants))|Hierarchy.all)\+?)?
((((DayAllocation.)?(first|last))|DayAllocation.all)\+?)?:)?(#[A-Za-z0-9\-_]+(\.(#[A-Za-z0-9\-_]+))*|(#[A-Za-z0-
9\-_]+\.)*
(ThisComponent|GlobalValue|Product|Product\.Brand|Product\.Accommodation|Product\.Accommodation\.SellingAccom|Prod
uct\.Accommodation\.SellingAccom\.Board|Product\.Accommodation\.SellingAccom\.Unit|Product\.Accommodation\.Selling
Accom\.Unit\.SellingUnit|Product\.OnewayFlight|Product\.OnewayFlight\.BookingClass|Product\.ReturnFlight|Product\.
ReturnFlight\.BookingClass|Product\.ReturnFlight\.Inbound|Product\.ReturnFlight\.Outbound|Product\.Addon|Product\.
Addon\.Service|Product\.Addon\.ServiceFeature|Brand|Accommodation|Accommodation\.SellingAccom|Accommodation\.Selli
ngAccom\.Board|Accommodation\.SellingAccom\.Unit|Accommodation\.SellingAccom\.Unit\.SellingUnit|OnewayFlight|Onewa
yFlight\.BookingClass|ReturnFlight|ReturnFlight\.BookingClass|ReturnFlight\.Inbound|ReturnFlight\.Outbound|Addon|A
ddon\.Service|Addon\.ServiceFeature|SellingAccom|SellingAccom\.Board|SellingAccom\.Unit|SellingAccom\.Unit\.Sellin
gUnit|BookingClass|Inbound|Outbound|Service|ServiceFeature|Board|Unit|Unit\.SellingUnit|SellingUnit))"/>
    </xs:restriction>
</xs:simpleType>
</xs:union>

There’s a bug in that regex that Stella needed to fix. As she put it: “Every time you evaluate it a few little kitties die because you shouldn’t use kitties to polish your car. I’m so, so sorry, little kitties…”

The full, unexcerpted code is below, so… at least it has documentation. In two languages!

<xs:simpleType name="SourceAttributeType">
                <xs:annotation>
                        <xs:documentation xml:lang="de">
                Die Source Angabe folgt folgender Syntax

                        source = ( Eigenschaft1+Eigenschaft2+... ":" ) ? steps

                        Eigenschaft1 = "local" | "global"

                        Eigenschaft2 ="real" | "virtual" | "ComponentType.all"

                        Eigenschaft3 ="self" | "ancestors" | "descendants" | "Hierarchy.all"

                        Eigenschaft4 = "first" | "last" | "DayAllocation.all"

                        Falls Eigenschaften angegeben werden muss zwingend die oben angegebene Reihenfolge der Eigenschaften eingehalten werden.

                        steps = oneOrMoreNameSteps | zeroOrMoreNameSteps | componentSteps

                        oneOrMoreNameSteps = nameStep ( "." nameStep ) *

                        zeroOrMoreNameSteps = ( nameStep "." ) *

                        nameStep = "#" name

                        name ist eine Folge von Zeichen aus der Menge "A"-"Z", "a"-"z", "0"-"9", "-" und "_". Keine Umlaute. Mindestens ein Zeichen

                        componentSteps ist eine Liste gültiger Werte, siehe im folgenden

                Gültige 'componentSteps' sind zunächst:

                        - GlobalValue
                        - Product
                        - Product.Brand
                        - Product.Accommodation
                        - Product.Accommodation.SellingAccom
                        - Product.Accommodation.SellingAccom.Board
                        - Product.Accommodation.SellingAccom.Unit
                        - Product.Accommodation.SellingAccom.Unit.SellingUnit
                        - Product.OnewayFlight
                        - Product.OnewayFlight.BookingClass
                        - Product.ReturnFlight
                        - Product.ReturnFlight.BookingClass
                        - Product.ReturnFlight.Inbound
                        - Product.ReturnFlight.Outbound
                        - Product.Addon
                        - Product.Addon.Service
                        - Product.Addon.ServiceFeature

                Desweiteren sind alle Unterschrittfolgen aus obigen Pfaden erlaubt, also 'Board', 'Accommodation.SellingAccom' oder 'SellingAccom.Unit.SellingUnit'.
                'Accommodation.Unit' hingegen ist nicht erlaubt, da in diesem Fall einige Zwischenschritte fehlen.

                                </xs:documentation>
                        <xs:documentation xml:lang="en">
                                The Source specification obeys the following syntax

                                source = ( Feature1+Feature2+... ":" ) ? steps

                                Feature1 = "local" | "global"

                                Feature2 ="real" | "virtual" | "ComponentType.all"

                                Feature3 ="self" | "ancestors" | "descendants" | "Hierarchy.all"

                                Feature4 = "first" | "last" | "DayAllocation.all"

                                If features are specified, the order of features as given above has strictly to be followed.

                                steps = oneOrMoreNameSteps | zeroOrMoreNameSteps | componentSteps

                                oneOrMoreNameSteps = nameStep ( "." nameStep ) *

                                zeroOrMoreNameSteps = ( nameStep "." ) *

                                nameStep = "#" name

                                name is a string of characters from "A"-"Z", "a"-"z", "0"-"9", "-" and "_". No umlauts allowed, one character is minimum.

                                componentSteps is a list of valid values, see below.

                                Valid 'componentSteps' are:

                                - GlobalValue
                                - Product
                                - Product.Brand
                                - Product.Accommodation
                                - Product.Accommodation.SellingAccom
                                - Product.Accommodation.SellingAccom.Board
                                - Product.Accommodation.SellingAccom.Unit
                                - Product.Accommodation.SellingAccom.Unit.SellingUnit
                                - Product.OnewayFlight
                                - Product.OnewayFlight.BookingClass
                                - Product.ReturnFlight
                                - Product.ReturnFlight.BookingClass
                                - Product.ReturnFlight.Inbound
                                - Product.ReturnFlight.Outbound
                                - Product.Addon
                                - Product.Addon.Service
                                - Product.Addon.ServiceFeature

                                In addition to that all subsequent steps from the paths above are permitted, that is 'Board', 'Accommodation.SellingAccom' or 'SellingAccom.Unit.SellingUnit'.
                                'Accommodation.Unit' in the contrary is not permitted, as here some intermediate steps are missing.

                        </xs:documentation>
                </xs:annotation>
                <xs:union>
                        <xs:simpleType>
                                <xs:restriction base="xs:string">
                                        <xs:pattern value="(((Scope.)?(global|local|current)\+?)?((((ComponentType.)?(real|virtual))|ComponentType.all)\+?)?((((Hierarchy.)?(self|ancestors|descendants))|Hierarchy.all)\+?)?((((DayAllocation.)?(first|last))|DayAllocation.all)\+?)?:)?(#[A-Za-z0-9\-_]+(\.(#[A-Za-z0-9\-_]+))*|(#[A-Za-z0-9\-_]+\.)*(ThisComponent|GlobalValue|Product|Product\.Brand|Product\.Accommodation|Product\.Accommodation\.SellingAccom|Product\.Accommodation\.SellingAccom\.Board|Product\.Accommodation\.SellingAccom\.Unit|Product\.Accommodation\.SellingAccom\.Unit\.SellingUnit|Product\.OnewayFlight|Product\.OnewayFlight\.BookingClass|Product\.ReturnFlight|Product\.ReturnFlight\.BookingClass|Product\.ReturnFlight\.Inbound|Product\.ReturnFlight\.Outbound|Product\.Addon|Product\.Addon\.Service|Product\.Addon\.ServiceFeature|Brand|Accommodation|Accommodation\.SellingAccom|Accommodation\.SellingAccom\.Board|Accommodation\.SellingAccom\.Unit|Accommodation\.SellingAccom\.Unit\.SellingUnit|OnewayFlight|OnewayFlight\.BookingClass|ReturnFlight|ReturnFlight\.BookingClass|ReturnFlight\.Inbound|ReturnFlight\.Outbound|Addon|Addon\.Service|Addon\.ServiceFeature|SellingAccom|SellingAccom\.Board|SellingAccom\.Unit|SellingAccom\.Unit\.SellingUnit|BookingClass|Inbound|Outbound|Service|ServiceFeature|Board|Unit|Unit\.SellingUnit|SellingUnit))"/>
                                </xs:restriction>
                        </xs:simpleType>
                </xs:union>
</xs:simpleType>
[Advertisement] Release! is a light card game about software and the people who make it. Play with 2-5 people, or up to 10 with two copies - only $9.95 shipped!

Profile

radarrider: (Default)
radarrider

August 2010

S M T W T F S
123 4567
891011121314
15 161718192021
22232425262728
29 3031    

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 20th, 2017 09:52 pm
Powered by Dreamwidth Studios