Fixed that for you.
Fixed that for you.
Unlike other CSS properties, custom property names are case-sensitive.
Fantastic! Let's make some things case sensitive and some things not! Genius! If you're going to introduce something new (like, you know, VARIABLES), you might as well make it break all of your existing conventions.
Now even better, here's how you define a variable:
And here's how you reference it:
Oh that makes sense. You declare it as var-name but then when referencing it you refer to it as var(name)! Wow just like that other language... ooh um... oh yeah NONE OF THEM.
Honestly this is the reason why web development is utter hell. Confusing and stupid standards that no-one bothers to stick to.
And why the hell can't I do width: 50% - 10px? What century are we living in again?
Hey guys, 99% of mastering these days has been brickwalled. The recordings that you're buying and downloading before encoding, at the mastering stage has already had all "the nuances, the soft touches, and the ends on the echo" removed. You can't get that back. In fact, all this device will do is make these artifacts more obvious.
Getting a 30 gazillion kbps FLAC file is utterly pointless when the same data can be represented in a 320kbs mp3 file.
I can personally guarantee* (*worth nothing, not redeemable for anything) that sound studios will not start producing multiple mixes just for the audiophiles. It's just not going to happen. People do not care about this stuff and are happy with their iphones/androids, so the sound studios are not going to bother.
Fixed that for ya. Remember guys, the internet is WORLDWIDE.
The Australian government has already received heaps of flak about phone tapping the Indonesian president's wife which was a very big deal. Indonesia were not happy. The president even took the unprecedented step of tweeting his displeasure. Then the Australian government decided it was a good idea to start towing asylum seeker boats back to Indonesia - they claimed the policy was to "turn the boats back" - turns out they've been actually towing them and going straight into Indonesian waters with our war boats. Stupid, stupid. Plus they "accidentally" did this 5 times.
And only two days ago some Aussie girl was just released early after having been locked away in an Indonesian prison for 10 years. This will have raised the Indonesians ire too. This will just give them another excuse.
In 2 hours there will be another spluttering prime minister on the TV trying to put this fire out claiming that it's nothing new, "all's fair in love and war" etc etc, but it really depends on how the Indonesians react - if the headline is "Aussie's listening to ALL our phone calls, 1.8 million keys stolen, collaborating with the US", the people will react and protest, the government will look weak in front of their people, and they will have to react.
I think there's going to be a bit of a storm about this one.
The brick wall analogy is not nonsensical. I bet there are lots of edge cases, requirement changes and mortar leaks to consider when building a wall.
A builder builds a wall. A week later, bricks begin to fall out of the bottom, but he continues to build the wall higher.
There is an important question here. Did the builder know any better, and should the builder be expected to know any better?
If this is something that is clearly taught in brick laying school, and the company expects their builders to conform to the rules of bricklaying school, and the person just knowingly willingly continued on, then the builder's company "technically" should suck up the cost. This is not the client's fault.
Whether the builder is fired or has to fix it outside of hours is a completely different question. That's up to the discretion of management. If the builder had continued on their merry way knowing they were doing the wrong thing, then asking them to fix it outside of their paid hours could be a good learning opportunity. Or if it's willful negligence then maybe it's a firing issue (if the building will fall down). Of course the best way to get them to learn their lesson is to show them the impacts of their work - now everyone has to stay back and fix their shoddy work, and they won't be popular for a while
However, if this is something that isn't taught in bricklaying school, but is something that only a bricklayer with 5 years of experience should know, and this dude was a fresh-faced apprentice, then the company needs to ask themselves "should we have had better quality control methods to stop this problem occurring earlier?". Should he have been supervised? Should he have been doing it in the first place? Should someone have inspected his work periodically?
This is actually quite a good question and not a silly analogy.
The next step is to try to apply this to software engineering. As we all know, building a wall and fixing up a shoddily built wall is quite a different thing to fixing bugs. Most (I would hope!!!) bugs are not caused intentionally or as a result of willful negligence. If a developer is committing work that is full of bugs and other people are building on top of that work, The same analogy applies as to the builder scenario. You expect someone to work according to their level of expertise. If they don't, you better start reviewing their work more often or move them to an easier task.
The best way to improve comment quality is to vote up the good comments. Not to make it more difficult to enter good comments. Look at stackoverflow. Great commenting system with a realtime preview, fantastic.
Some of the comments use font size 0.85rem (never heard of REM before for a font size), and some of them use 1.5em. Can't work out why some are different. Don't care either.
Scrolling through the comments the big problem is that the important stuff, like you know, the actual content of the comment, isn't given prime position. It's hard to find the actual comment inside all of the "subject, commenter, whitespace". It's hidden. Stupid, very hard to read. Notice how reddit comments the actual comment text is bigger? That's so you can read it. They should also condense the subject into the "who" section, and be in the same line. There's enough room.
Oh and I can't see the member ID now of the commenter. That sucks. I liked looking at it to see how long the person had been a member for.
I like the "comment threshold" gears icon to make it easier to filter per level. But damn, it uses Ajax. Could be nice, but I bet if it runs on a post with 500 comments it's going to run slower than a snail. When I choose one of those thresholds I just get a "load more" button - what the hell? There's nothing to load. So those filter options are pointless as well if there's nothing to show.
Ok I can see what people are complaining about now.
I don't like the fact that there are two boxes, and neither are labelled. It's obvious to me that the first one is a subject but it's not explained. Not a good UI.
The "From you're-grounded dept" is below the article, that doesn't make sense.
The comment box isn't a wysiwyg editor. Can't I just highlight text and hit control-B and make it bold? C'mon, this is 2014, we had this functionality 20 years ago.
Menu bar static at the top of the screen? Pointless. If I need that I'd scroll to the top.
Ok I've previewed my comment... newlines aren't converted to BR's. What the hell. Apart from a slightly different CSS what the hell is this beta all about?
I was so happy to ditch Java after 2 years and move to
Hands down, Eclipse was the slowest and most confusingest I've ever used out of ALL of the above.