bjornsteffanson

Kowloon Dog City.

Then you're going to love every other Korean website, too.

Typing this response from downtown Seoul, and can confirm that censorship is very prevalent. There are thousands of blacklisted sites -- they are simply forwarded to http://warning.or.kr/, which reads "This site has been legally blocked by government regulations." The numbers on the table below are different agencies you can call to appeal the block if you think it's unwarranted. Most people who are annoyed by it just VPN to Japan and ignore it.

I spent an embarrassing amount of time scratching that asterisk wondering how my screen got so dirty.

This is absolutely fantastic, and thoroughly technical -- particularly the SPICE simulations. After becoming equally engrossed in designing a "perfect" microphone capsule, I'm tempted to build one myself.

This was written 12 years ago -- I wonder how the author feels now. Specifically I'm curious if the author is still contented with the equipment. Also, apropos of nothing save for sheer curiosity, I'm interested to know what input media (i.e., specific recordings and formats) and output equipment the author used (or uses) for both testing and pleasure.

Some of these examples are valid and should be common knowledge for all web developers (e.g.: treating CSS semicolons as terminators rather than separators; transitions; unitless values; all [+1]), and some of these examples are a bit questionable. The code style seems a bit esoteric, especially some of the ES. Also, not many of these examples would pass an HTML validator without warnings due to the lack of quotes surrounding attributes. Just a caveat..

It's not different, and I believe that was the point. There is a weird stereotype that I've encountered about Sweden that I wasn't aware of until the first time I lived outside of our country...whenever something like this comes along, there's a notion that some people think "Oh it's Sweden, they'll do the right thing," as if our laws or courts are somehow "more right" or "more just" than others. I think what the preceding comment was trying to point out is that that is not always true.

Your assessment of the emerging front-end skillset is spot on. For better or for worse, if js frameworks are here to stay for the next few years (and it seems they are), the programmers who got in early are going to clean up as they are now sitting on 1-3 years of experience.

I did misunderstand - apologies.

You should check out Bourbon Neat: http://neat.bourbon.io/, or leverage Sass' @extend directive.

Your CSS could easily be shortened to:

  .body {
    @extend .container;
  }

  .nav-header {
    @extend .row;
  }

  .my-logo {
    @extend .col-sm-2;
  }

And your markup could be much cleaner:

  <body>
    <nav class="nav-header">
      <div class="my-logo">
        <!-- your stuff -->
      </div>
    </nav>
  </body>

Some too good not to share:

- Your Username Will Now Have Amazon Ads Pre-Installed

- Android Ported to ANSI C

- Memories of Stasi color Germans’ view of time, if nanoseconds were seconds

- Cook something or get out of Facebook.com

- Mark Cuban: If you want to order it, use 'view source' to find the commented-out link.

- How Little Sleep Can You Get From McDonald's?

- Ocean acidification due to SOPA

- Love startups but not a developer? We need Ruby developers

- Lenovo CEO Gives His $3 Million Bonus to 10,000 Users in 1 Month (with stats)

A lot of it has to do with the culture of shame that causes us to posture in the first place. We bullshit because we're afraid of what the other person's reaction will be like.

I feel fortunate to work for a company that has a zero-tolerance policy for shaming others and their code knowledge. In fact, it's much more common to hear something like "I'm not familiar with that - could you teach me?" instead. Weekly, we show off new tools or techniques we've discovered so the chances of being left in the dark are slimmer. It leads to a lot more open discussions and a better overall base of knowledge across the entire company.

So I currently live in Tennessee near where the incident took place (the vehicle owner is a relatively well-known spinal surgeon in Nashville) and I can tell you that the interstates in this part of the country are relatively desolate and do not present an attractive option for pulling over. Outside of the cities, there are miles between exits and the area is heavily wooded with little amenities nearby. After having driven on I-24 for a time, I can relate with the author when he states "I just wanted to make it home". If his car seemed "driveable" at the time, I too would've chalked it up to bad luck and tried to survey the damage at home rather than getting stranded on a interstate shoulder. Just a hypothesis offering some context for the basis of his decisions.

The company I work for has 33 employees, 16 of which are developers. We have the choice to work remotely. We use GitHub for code, Google Docs/Drive for document storage, and email, IM or Google Hangouts for communication - haven't found a need for anything else. There is a small office in the company's "base city" where a handful of employees work full-time (by choice), but the rest are remote throughout the region. Most of us are within a 1 to 2 hour drive. We gather at our space once or twice a month to catch up, show off new ideas, and hangout over a few beers - it's not a mandate, just whoever can make it. I'd say there's a 95% participation rate. We've found it takes the right employee to handle this environment - someone with a lot of drive and accountability. Bad apples shake down pretty quickly. A new hire will drive (or fly) to the office and spend 2 - 3 days in town getting his machine set up, filling out paperwork, training, meeting the rest of the team, etc., then head back out and work from whenever and wherever he/she likes.

We have a policy that unless you declare you're "out of the office" (i.e., vacation), you should be generally available between the hours of 9-to-5, should someone need to contact you. In practice, though, to avoid being disturbed like that, we've found that we've all become excellent communicators and will set expectations appropriately for our co-workers. To date, not one of my co-workers has called me if I've been out during 9-to-5 because they needed me.

This is not a rant, because it's the truth. To outsiders, this attitude seems hyper-negative because it's difficult to comprehend the level of ineptitude found in federal government IT. As a non-national who has done some (very non-sensitive) on-site IT work for the U.S. government, I experienced this firsthand for several years. (And before I get accused of elitism, my home country doesn't necessarily have the answers either.)

When all of the Snowden and PRISM stuff broke, my first thought was to chuckle and ask, "How?" Based on my experiences with federal IT workers, it's hard to imagine there is a room of crack coders underground in some basement or deep inside some mountain just knocking it out of the park.

Ah, I think you may be right on that one. Perhaps more accurately we could say he was just acting Scandinavian. :)

Geographically, sure. Culturally - not at all.

As a Swede, it seems to me he's just acting Swedish.

It probably doesn't, at this point. In fact, I bet they're probably trying to figure that out right now, and likely know already. I think the line "...and this is just the beginning." is very telling. Premium recipes or financial kickbacks for lead generation to other services seem like potential ideas for generating revenue in the future.

While I was playing I was thinking "It would be nice if they tracked the sequence in which answers were selected." On several questions, I immediately clicked a few that were obvious and then the rest I was like "...and maybe this one?"

Another important point to consider is that the future won't be available to everyone at once - money will prohibit that. I wonder at what point will touchscreens become "old fashioned", and I'm sure they'll see (limited) use for long after that.

Daunting. I made a mistake, and am literally paying for it. It's not that I feel the degree itself was not worth it, but I chose my path poorly. I could have just as well gone to a public school and received an equal or better education than a private one. That rude awakening did set a more intense course of determination for the rest of my life however.

Not a joke, but my first language isn't English so I'll own up to the poorly written part. I think I was trying to point out that it seems he copied the actual photographs of the magazines from somewhere because he admits to not owning them.

I wonder if the images of the magazines were copyright-protected themselves since it appears he didn't actually access them firsthand.

Can you define 'shiesty'? Not having a go, just haven't heard that word before, and searching returns conflicting results.

I don't think so. More than likely, English is not the author's first language. As a one-time ESL teacher I noticed that students from other cultures often used exclamation points in place of where a native English speaker would have simply used italics. That is to say, they use exclamation points to indicate emphasis rather than excitement. But who knows, maybe the author just really is excited about their topic (!).

My view scares me, too, but I think you have the right idea: It's a terrible business decision. Much like the Netflix/Qwikster ordeal, I imagine the result to be some sort of mass exodus.

Obviously, our use of any application is simply a privilege, and participation is not compulsory. As creators of the application, it's Instagram right to control their application how they see fit.

That point is easily overlooked. It's the principle I'm defending, not the decision.

My hope is that great companies will make great decisions. I think we've seen a little bit of that from organizations like Google and MapBox doing the "right thing", and they have great products to show for it.

Technically we _are_ giving our consent by using the service. In fact, we already agreed to the current terms, which state "We reserve the right to alter these Terms of Use at any time." It's not even a classic bait-and-switch. It's clearly stated in the contract we all signed up for.

I agree that it's sort of uncool on Instagram's part, but as fellow app developers, shouldn't we also be siding with Instagram for their right to protect the interest of their product?

I hate to be the guy that points this out, but it's an important distinction.

I absolutely agree. My last and current employer both offer unlimited vacation. For whatever psychological reason, I find myself taking less vacation than I did when I was _earning_ it at my McJob for the rate of 6.33 hours every month.

If you are such an employer, please consider setting a realistic expectation of what is an appropriate amount of time-off. If there really is no limit, then please consider more intensive training with regard to your company's culture .

This is an entirely valid point - not sure why you're being downvoted. I recently participated on a project with a client whose product name was synonymous with an alternate spelling of a rare skin disease.

We brought up our concerns about it in development, but they resisted. Their product displaced the skin disease search results in a matter of weeks after launch.

My point being: names are just names, but they can make or break through connotations depending on how well delivery is executed.