mazatta
mazatta on Hacker News
This is one of those things that I always assume other Python developers know about, but often don't.
No, Arrow is much more than parsing/formatting.
Each Arrow object has a `shift` method, which is how you can add or subtract units of time. Greater/less/equal comparisons work exactly as you'd expect them to.
This vector has always existed - all that changed is RFC 8484 defines a standard way of doing this.
A former coworker accidentally bought one of these on Craigslist thinking he was buying a legit one. The price was pretty close to retail (or maybe even higher, as it was close to the X launch). The seller even let him handle one that "had already been opened", which was likely a legit one and then what he ultimately bought was a sealed fake.
Most of the elements you'd want on a status page are there, but the tone and structure are really off. I think you nailed it that this reads like an internal communication to a manager, not to a customer.
I knew this was coming eventually, but I am definitely selling my Rift after this announcement.
The only Datadog feature announcement I look forward to is "we've solved our stability issues!".
I am sick of playing the "is our infrastructure or Datadog's on fire?" game at 3 AM whenever I'm on call.
I can only imagine the firefighting their engineering teams are dealing with, but for what you pay, I expect better.
It feels like someone's hackathon project that was accidentally deployed to production, and has been running ever since.
It does make sense to impose some sort of upper bound (only so someone doesn't try and DoS you with a crazy long password), but 13 characters isn't going to bring a server to its knees.
Apologies to the authors, but anything from Packt is a hard pass.
I had the same experience - radio silence.
Are any of these an option at the Vancouver office?
A good PM knows that all they should own is the definition of "what" should be worked on, but the bad ones seem to gravitate towards the "how" as well. I suspect this has something to do with many PMs transitioning out of engineering roles, but it can be very frustrating to work with a "Product Micromanager".
Airbnb is a zero sum game - what tourists win, locals lose.
Two of my coworkers are currently being forced to look for a new place to live in a tight housing market because their current landlord can make more money renting on Airbnb.
I've stayed in Airbnbs in the past (and appreciated the convenience), but I no longer will.
Of all the books I recommend for junior/intermediate developers, this is the one I demand they read. I wish the the free online version was still available, but it doesn't appear to have survived O'Reilly's switch to the subscription model.
They charged my card long after I'd already canceled and changed providers. Eventually got a refund, but I shouldn't have needed one in the first place.
I was really interested in applying recently, until I saw what their interview process entails, and laughed. I can understand "hire slow", but 7 rounds of interviews is way too much to ask of candidates, and indicates a navel gazing culture I want no part of.
Exactly. I'm curious if the author continued using Go for a bit of time, if they would still write the same article.
Some of the concepts the author took issue with, such as receiver arguments or multiple return values never felt all that unusual for me, but that's probably because I'm quite familiar with a language like Python, where these concepts are pretty common if you've ever written a class or written a function that `return a, b`
The final argument, that Go's concurrency is somehow not concurrency, or all that special is a bit too much for me. That section needs some editing, but if anything, they unintentionally make the point that Go's concurrency IS simple.
Now they can lose your money, along with your data!
If I could set arbitrary key/value on both users and features, that should be enough to make it work.
It looks interesting, and might be something I introduce to my team.
Is it possible to define cohorts of users, and then expose features to that group? I work on a SaaS app used by businesses, so it'd be very handy to use this tool when a customer is beta testing a new feature.
The retry and locking mechanisms look pretty handy - I've had to implement those on my own whenever I've used Celery.
What's your experience been using this and Redis for your queue backend?
I've worked on codebases that use a similar thing, and I have yet to see one where this wasn't a mistake.
Most of the time, this probably gives you exactly what you want, but then there are times where you discover bugs in production because data you assumed is your custom class is a plain old dict, and now you're raising AttributeError all over the place. Another wart is if you are unfortunate enough to have keys that match the name of one of dict's methods, then you have to resort to instance['items'], which defeats the purpose of using this in the first place.
This is a fun trick, but if someone one my team tried to introduce this, it won't make it through code review.
No operating system can protect your machine if it is left unlocked - even allowing physical access makes you vulnerable. A worthy concern, but not in itself an "Ubuntu problem".
That's quite true, but that development is only able to happen in very tiny bands of the city, and there is a cap on how tall new buildings can be.
The vast majority is zoned for single family homes, and any kind of densification is resisted vigorously by existing property owners. E.g. http://www.cbc.ca/news/canada/british-columbia/commercial-dr...
There's no question Vancouver is building, but it is not building enough of the right kind of housing (i.e. rental, non-luxury, and > 1 bedroom units).
If the author is reading this, the social sharing buttons on that page are very annoying. On my browser/resolution it covers up the first character of every line it touches, which makes reading the article without resizing the window nigh impossible.