timme

Also, the population segment that matches all three conditions will be far from 'micro'.

By the geniuses that brought us ePrivacy Directive and GDPR. Might be cheaper to just tell tech companies they're not welcome in the EU.

It's not tainted in Europe either. Sales are healthy and you see cars from the full range (Skoda, Seat, VW, Audi) aplenty. The overlap between car buyers and outrage bubble subscribers might be limited.

No it's not. Most of them are E-classes.

Good post, but that pie chart, man.

In future posts of similar nature I suggest clarifying visualizations with labels, or moving the legend much closer to the chart.

I have nothing to do with the Rust language, but here's what gave it away for me:

- giant rusty-looking "R" logo

- "... you can use Rust for ..."

If you're in the market for "simple" solutions like this, do yourself a favor and spend one afternoon with d3.js.

Pre-packaged chart solutions will never achieve 100% of what you're trying to do because the options for customization of charts are endless.

Learning the basics of d3.js will liberate and empower you.

This is a fantastic place to start: http://chimera.labs.oreilly.com/books/1230000000345/index.ht...

If you're a web developer you can start at chapter 6 and stop as soon as you know enough to do your thing.

Generic charts with a blue/orange color scheme. Clickbait bullshit.

No more dealing with SQL or other finnicky languages. Everyone's happy when your developers are happy.

SQL a 'finnicky language'? Are you for real? Jesus.

To create a good (i.e. actually useful) bot you want to start by spending a lot of time in whatever game you're targeting.

Most bots, or trivial helpers like macros, are written by the players that have spent a lot of time in a game and identified the elements most worthy of automation. The player's lack of in-depth technical knowledge then leads to the mass of crappy bots out there.

If you're coming from the opposite side, i.e. you have technological knowledge but don't know where to start, all you're missing is domain knowledge of an individual game or genre to figure out what you actually want to build.

Edit: it's also worth noting that game AI and bots are pretty different problems.

If a 4 word claim with a few overstyled charts qualifies as research then we're doomed anyways.

Bootstrap started out as framework for internal apps.

Pretty sure $1k doesn't buy the in-depth product understanding that is required for a good landing page.

still happy i paid for pinboard a while ago.

the "no-nonsense, speed first" policy and the fact that it's actually being executed are my favorite things about the service.

finally. shame it's not written in the much more scalable coffeescript.

font-weight: 200;

Don't do that.

There's nothing painful about a regular form with the minimum amount of fields.

The review is about the PB287Q, your amazon link is for the PB278Q.

The upsides remain the same, but in small teams there is less pressure to go for a component architecture, so you have to come up with the discipline to go through the extra effort initially.

the last carousel you'll ever need

(requires jQuery 1.7 +)

yeah... no.

if you really want to deliver on that claim then make it a vanilla JS component.

You can see the results here:

https://docs.google.com/forms/d/1MsHsMskdVWzFebVIltHogUBuR8I...

As the voting seems to have mostly calmed down, here are the results.

https://docs.google.com/forms/d/1MsHsMskdVWzFebVIltHogUBuR8I...

- things like "first-paragraph" are better written as classes.

- things like odd-even should be implemented with pseudo selectors.

All of the things you mention are completely optional for the employer.

LESS/SASS are not what the post is referring to.

Re 2:

Never, ever handle output files directly.

Re 3/4:

So far I haven't seen a single useful thing that SASS doesn't process. Chances are that those attributes/hacks aren't something you want to have in your CSS to begin with.

As someone else has mentioned: SASS is an amplifier.

If you hate or don't get CSS to begin with, stay the hell away from SASS.

If you do serious work with CSS, SASS will probably help you solve things better.

I'll take data over bullshit articles like this any day.

"Feature Description: 146 hours."

If that is your core message then you have succeeded.

In Berlin: no problem. In the rest of Germany: probably problematic.