sharpercoder

The first realization about URI's being UI I had when I was looking to the first billboard with a URI on it - it must have been around 2000 or so.

Tables are generally a very good idea for languages. SpecFlow/cucumber as most notable example, but I can see others benefitting greatly as well.

I very much enjoyed the speedruns of this game done by CapnClever on twitch. He has records on most official games and also has run some of the unofficial games.

It great to see someone running through levels I sweated blood and tears on as a kid.

https://m.twitch.tv/capnclever/profile

Checkout the Googlezon clips: https://www.youtube.com/watch?v=AT9ho2G0N_Y and https://www.youtube.com/watch?v=OQDBhg60UNI.

The thing with an O lock is that is locks the rear wheel. A chain lock then can lock both the frame and front wheel to a pole. Although not 100% safe, most thieves will look for easier targets.

>This code wouldn't compile, for starters.

Thats the point. You need an `IValidator` interface.

    interface IValidator<T> {
        bool Validate(T thingToValidate);
    }
    class ThingValidator : IValidator<Thing> {}
    class ThingValidator : IValidator<OtherThing> {}

    var validators = GetAllValidators();

What type is `validators`?

>less guilt about taking vacation

This, and make it clear in various forms (email, several personal meetings, via wife, via friends, et cetera) that any outcome of the state of the company after return is okay. It's the only way to ensure the vacation is effective: vacation with guilt is having a lot less effective vacation. "Freedom" (from the company) must be felt.

It is not only good advice, it is required in fair amount of situations because of limitations in the C# language.

AsciiDoc has a serious adoption problem compared to MarkDown.

I notice a trend in my environments where an acknowledgement went from "okee" (Dutch) or "okay" to "OK"/"ok" to now just "k".

Contrast is clearly suboptimal. Lots of multigrey use in controls and noncontrasting colors in colored items. This would not go past our UX team.

This feels a lot like the good old framework/library debate. Instead of providing everything for the learner in a framework-y way (user must adapt, we call you), it seems better to offer lego blocks instead. Well documented, componentized, reusable things which can act as parts of any new system.

I remember trying so hard when I was a little kid to learn english and move on in any textbased game. I always failed. So I guess it's still easy to have dead ends in textbased games ;)

A presentation app where the cursor can be changed to a laser pointer (big red dot).

Reminds a lot of shapecatcher (shapecatcher.com): Unicode character recognition by drawing.

>Are the arguments to memcpy in the order of source, destination, length; or are they destination, source, length? Is strstr haystack, needle; or is it needle, haystack? Many individuals develop a habit of consulting references (such as system manuals) as soon as the question comes up.

I've always found this particular problem solveable by allowing programming languages having syntax in the form of

    public void CopyFrom(int address)To(int address)OfSize(long size) { // impl }

instead of

    Copy(int fromAddress, int toAddress, long size)

Are there good reasons why languages haven't adopted this syntactic nicety?

When I was about 15 years old, a friend tried to convince me a traffic light in front of his house was always green. I never believed him. Fast forward 15 years later. I moved to an apartment, cycling past my friends house to go to work. After a few weeks, I started to notice a traffic light which is always green! It was the same light my friend told me about. I remembered.

It is here: https://goo.gl/maps/2cgcx1b92LL2. Streetview direct link: https://www.google.com/maps/place/52%C2%B000'00.9%22N+5%C2%B...

Keep in mind that serif typefaces do not always render pleasingly to the eye as they need more pixels to render correctly. These pixels are needed to render the subtle serifs. Monospace and sans typefaces suffer a lot less from this problem.

It is one of the reasons I never advise to use serif fonts for text body. Nowadays, betterresolutions are used more often, but low res displays are still common enough.

> perfect is the enemy of good

The more threading code I have seen, the more convinced I become that it should be avoided at all cost. The pitfalls are nonobvious and potentially incurring datacorruption. Rather, they should be behind understandable abstractions (like await/async and Task/Task<T>, but those have their own pitfalls) where applicable. Also, I can see value in an "unsafe" block (e.g. a "threading {}" keyword) where the writer of code communicates to the reader "inspect this with special threading awareness"

My experience is they actually do deliver promises, yet always too late. It was the case with the 120Mhz 80486, the K6-2, the Athlon, the Opteron, and I'm just getting started. All about as fast as their marketing claimed, but simply too late so the nextgen Intel caught up for the most part.

I remember setting up 4 prototypes on 4 different platforms: sun jvm, adobe flash, dhtml and .net. The last won, mostly because ease of development and fast DirectDraw rendering of many datapoints. Never looked back, best decision in my career.

Note that this goes for all levels: variables, functions, methods, classes, namespaces, libraries, software packages, systems, business (world?).

what features/behavior would you want to have it qualify as such?

Show value.

1) Show value you have added to OSS in an easy digestable way for potential employers. A 2-minute checkout on the web, with explanations where needed to have people understand what you did.

2) Show value you can add to their business. Place yourself in the position of the businessowner, and match this with your skills and talents. Eloquently writeup what value you can add to their position in the business.

I've seen it popping up a lot lately. It's used as an identifier for lambda functions, indicating "i must use a variable identifier here, but I don't use it"

someObject.doSomething(_ -> isDerp());

> If computers are good at anything, they are good at parsing code and analyzing it. So I set out to make this work, and prettier was born. I didn't want to start from scratch, so it's a fork of recast's printer with the internals rewritten to use Wadler's algorithm from "A prettier printer".

Bob Nystrom (munificent) disagrees[0] after writing one himself:

> The search space we have to cover is exponentially large, and even ranking different solutions is a subtle problem.

[0]: http://journal.stuffwithstuff.com/2015/09/08/the-hardest-pro...

This community thing may be the case, it doen't bring in any dollars. At least not at any signifcant scale to continue developing the platform.

What the world needs is an easy to use web publisher, the Microsoft Word for the Web. Sure, we can type text and publish that. We can't however add in math formula's, pictures, excel sheet (parts), word document links, slideshows anything digital really, with "unexpected simplicity and ease". There's always pain involved, and I know individuals and companies are willing to pay heavily if these problems are solved in an online publishing tool.

The community is now just there to generate critical mass for adoption, and used as highly critical feedback userbase.

I really want to have an extendable Markdown. A standard mechanism for expressing a used extension and providing an implementation for the Markdown processor to apply a transformation.

This standardization can then result in much improved support for Markdown editors. Think autocomplete for any extended item which works on any Markdown editor.