ts330

Not going to lie, I read the title as the Art of Fishing... and spent the entire article waiting for the finale where some how this was an analogy with fishing...

came for the fish, stayed for the all-too-familiar feeling of incomplete projects.

How Twitter (nascent at the time) has changed… let alone the technology landscape and the wider world!

Exciting? Possibly for those involved.

I hate to say this, as I'm generally optimistic towards most developments like this, but over the last decade I've become so apathetic towards anything and everything from Google. They've lost so much mindshare and credibility. Their org structure leads to stagnation left, right and centre.

I'd rather tolerate the poor status quo in React land than take any sort of bet on Google getting something "newish" right.

It wasn't always like this.

its arcane syntax and tendency to behave in unexpected ways is a massive barrier to entry. you spend way too much time trying to figure out the edge cases to command outputs / errors / what-happens-if-the-output-isn't-as-expected (usually due to error conditions.) scripts need to be reliable and predictable (without fuss!) - especially if you're controlling things with them.

sorry, the UK sarcasm mark-down doesn't always render correctly...

Surely this will become a non-problem as we migrate to NOSQL... no...? oh? we're migrating back? great.

Who are all you crack-junkies, running SQL queries against live...? I've seen enough literature saying we don't do this anymore... ooooooooohhhhhh. right... yes, the people writing about that aren't the ones actually shipping and making the clock tick ;-)

the explosion of threads is because of twitter's algo...

to view a thread, you have to interact with a tweet. this interaction drives metrics that results in the tweet showing up more frequently in the algo-feed. the multi-post nature of a thread means there are more opportunities to "like/retweet" - which also drive the algo-feed.

all this increases follower count... and an audience (that's soon to be easily monetisable on twitter) is far more valuable than a blog... unfortunately

basic manipulation in CF is an absolute pita - so much overhead for simple things like clobbering a header value.

but by allowing JS/whatever, it gives you an infinite landscape to work with the values in a language that a wide range of people grok.

it's just a matter of getting a decent deployment setup so you can rinse and repeat easily.

but i agree, it's a freaking jack hammer where most people need a small tack hammer.

Happy customer of RevenueCat. Integrated and never looked back.

this is a MASSIVE selling point, BUT, when your users contact support trying to gain access to their account and can't describe what their email address might be... trust me, there is pain in your future.

Question: had Microsoft chosen a less ridiculous sounding name to begin with, would it have been more popular?

... and will be shutdown in about 18 months when our attention wanders elsewhere ...

interested to know your approach to long leases lasting more than 60 seconds (if you have this?). do you go for continual renewing (and bailing out if you get too close to the timeout without getting a renewal). or do you go for infinite with your own break logic?

Well Microsoft had their annual mail outage the other day... I guess they could have coordinated a bit better to get them done and out of the way at the same time.

Just because people are searching for it doesn't mean it's popular. It means people are trying to answer a question about it. I'd posit there is more of a correlation between searches and newusers/issues/problems with the tool/language than how much it's being used. Stack Overflow is a better source for these stats anyway.

Nice, hadn't seen that. I like the comment at the end...

If approached in the right spirit, GDPR compliance can be a win-win for email marketers, quite possibly providing a much-needed correction.

What's interesting here is:

- this is the first confirmation I've received from a company stating outright that they're not going to be GDPR compliant and you should stop using them if you need to be.

- they're explicitly saying it's too much effort to store data in a compliant manner and ensure their processors are complaint. this possibly raises some interesting questions about what exactly they're doing with the data they have today.

- this GDPR thing is like async code, once it gets into a system it has long tentacles. I don't think this company fully realises just how many companies need to be GDPR compliant to continue doing business online. if you're in the SAAS business, it's very likely you're dealing with EU customers - or at the very least a customer that deals with EU customers, or an customer of a customer that deals with EU customers. You get the point - this tentacle keeps reaching down. You may think you're not excluding many of your own customers by not being compliant because THEY aren't EU-based, but it's their customers/controllers etc that require them to be compliant and thus you.

This tentacle is all encompassing.

hard to fathom there's an entire generation of developers out there for whom this is entirely new magic. there's an entire class of problem and suite of (bad) tooling that they're having to grapple with to deal with things that simply aren't issues in statically typed languages.

Roughly 1/3 comes from Intelligent Cloud (i.e. Azure and friends)... although revenues increased 93% in FYQ3. https://www.microsoft.com/en-us/Investor/earnings/FY-2017-Q3...

[edit: fix Intelligent Cloud vs Azure specifically]

I suspect this will lead to ads not being served via the site's code own code, but rather by Chrome overlaying the ads into the site using placeholders defined by the site.

By controlling the ad experience at this level (and this possibly being the only way to avoid being blocked), Google can enforce an ad-experience that is akin to in-feed facebook ads.

It also provides a far greater level of security around the ad unit and a far better level of accurate targeting (cookies don't get used, your login does). These two things together provide a new way to interact / monetise those ad units.

i love that he has 20 different shoelace knots! life was too simple before now.

lovely.

the sooner i can remove skype from my life the better.

that said, why can't any of these phone systems deal with the use case of two people trying to call each other and then simply auto connect the two calls? why does one side have to drop the call and answer the other?

enjoyed that, and i don't usually play any games what so ever.

totally misleading title... there was no signal at the time because they were still waiting for it.

Then they send you emails (from some random non-official looking domain) with password protected PDFs and ask you use bits of your account details to open it. The opportunity for phishing is insane.

how much does it cost to setup a factory to produce a half decent printer-scanner with ink cartridges and ink supplies? this entire industry is broken. surely basic printers are so well understood by now that every component is a commodity?

for the majority of people, a printer that simply just works is good enough. you do not need to upgrade every year. you do not need the latest in ink technology - you want photo prints, do it properly online.

manufacturers like HP et al only introduce different printer models / cartridges / drivers etc etc to keep people upgrading.

so, what's the cost of doing this? i'd consider it a gift to humanity.

Only 129 backers with 6 days to go?

This sounds like the type of project everyone should be supporting - unless I'm missing something and there's an alternative that's more secure and optimised than ImageMagick?

the key here is that more than one person is filling their tray at a time. so if one person is taking their time, other people can jump past them. obviously it helps to have motivated and efficient operators, but in my experience, it's almost always some dithering idiot that holds things up. as as we all know, serial processing of a queue is not efficient when you end up waiting on IO :)

You're right about learning. Everyone should be doing this ALL THE TIME. Problem solving and learning ability are what you should be measuring and then deciding if their past experience justifies the position/starting rate. This is far more likely to serve you well than testing the finer points of some algo/tech that is simply a building block of a solution to a far bigger set of business/technical challenges.