Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pydry
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
2039 ms
·
6331.
▲
by
pydry
7y ago
The story of diapers.com is probably as clear cut an example of predatory pricing as you could get: https://slate.com/technology/2013/10/amazon-book-how-jeff-be... The whole point of predatory pricing is that
6332.
▲
by
pydry
7y ago
I'd consider any datetimes that have an implicit timezone that isn't or might not be UTC a bug in any system. This isn't restricted to python. Servers that spit out logs with timestamps, for instance, should be spitting o
6333.
▲
by
pydry
7y ago
Vendor lock in is very expensive. At the moment vendor lock in is providing AWS with more profit margin than Amazon's entire retail division. It's more profitable than McDonalds. It's also A) frequently not all that hard to a
6334.
▲
by
pydry
7y ago
I'd say that: * About 70-80% of what you want to do with a service like appflow to integrate with a service like salesforce will be possible. The other 20-30% of your requirements will require building a bugging in house integration fr
6335.
▲
by
pydry
7y ago
>What does the library do? Throw an exception? Associate an arbitrary timezone (e.g. UTC)? Associate the local, current timezone? Naive datetime is what datetime.utcnow() returns. UTC is essentially a "default" timezone. I&#x
6336.
▲
by
pydry
7y ago
https://github.com/crdoconnor/strictyaml - typesafe YAML parser (solves the issues mentioned in 2 and 1).
6337.
▲
by
pydry
7y ago
I don't want a git client for exactly this reason. I wouldn't mind a staging / commit client though, or a client that visualizes the branch situation though. I wish people who made these things didn't start off with the
6338.
▲
by
pydry
7y ago
>With all the projects I've worked on, I've always found unit tests to be the best possible place to catch bugs and errors Have you considered that that might be due to the nature of the projects you've worked upon rather
6339.
▲
by
pydry
7y ago
However, the further down the pyramid you go: * The more unrealistic the tests generally become (larger % of false positives - tests that fail when they shouldn't - and false negatives - unit tests that simply don't catch bugs at
6340.
▲
by
pydry
7y ago
I've had bugs when doing webdev stuff in docker that didn't crop up under one kernel that cropped up when using another. It's rare but it happens.
6341.
▲
by
pydry
7y ago
Thanks for the vote of confidence. fwiw version 2.0 of strictyaml will feature its own specification and parser.
6342.
▲
by
pydry
7y ago
Making it the snapshot behavior based and comprehensible to the product owner helps with that.
6343.
▲
by
pydry
7y ago
>Snapshot testing is useful for catching regressions and nothing else. Visualizing and eyeballing snapshots in behavioral tests is a highly effective way of catching bugs and defining behavior (edit code - run test - verify output is cor
6344.
▲
by
pydry
7y ago
I did this once on a large project I recently joined. It took a long time to build these sophisticated mocks (3-4 weeks) and it was a fairly hard sell but it did have the advantage that it's somewhat immune from mythical man month is
6345.
▲
by
pydry
8y ago
I worked with some lawyers on some legal (finance based) automation based work and they weren't overtly resistant to automation at all, but it was fairly self evident that they were used to over-complicating everything - e.g. creatin