1,632 karma · joined May 4, 2012
It's co-written by the DuckDuckGo founder, and as an engineer who is thoroughly tired of marketing "hackers" who justify expensive campaigns with hand-wavy nonsense, this book changed the way I view marketing in general.
If anyone has more information than my 3rd hand comment, I'd be super interested. I was very disappointed not to find one for sale for a reasonable price. I would have loved one.
C++ needs a linter that rejects code that doesn't meet a certain standard ala Rubocop.
Of course it can't happen by magic, and you rely on the authors of the timezone libraries (a thankless task in itself), but if you remove a dimension of your data, nobody can ever help you.
The example (which is not so uncommon) that an appointment is set in timezone X, author of the service storing the appointment helpfully converts to UTC, timezone of the originating country changes and then the "return" from UTC to source timezone is incorrect, because now UTC-0600 is actually UTC-0700.
In short, any conversion that reduces precision is flawed. Dropping timezones after normalizing them to a canonical format makes it impossible to restore the conversion.
The result was sufficiently confusing that we threw it away, but it was helpful to get an idea what we were looking at, and why. We rebuilt the stack from hand, using all the files from the kompose tool as a guide/reference.
Later we found that kubectl can dump yaml, I found `kubectl .... -o=yaml[ ...]` to be super helpful, for any command you run from the tutorial or elsewhere, it'll generate you the equivalent YAML which you can commit/apply at your leisure.
I'm glad the tool existed, but idiomatic stuff in docker-compose is unidomatic in k8s (namely secret handling is completely different) which is a hurdle, and the "links" concept as used in docker-compose is essentially absent from k8s for our purposes (and, replaced wth much, much better and granular dns services and "expose"s)
Also, seconded the rOtring series mechanical pencils are astoundingly good, I'm always close to mine, I never travel without it.
- https://www.wired.com/2016/11/block-ultrasonic-signals-didnt...
(not trying to spread FUD, endorse this practice or criticise in anyway, just trying to help the parent comment understand one potential "excuse" for an app "needing" this functionality for a non-obvious use-case.)
(replied to the top thread, but it's applicable to everyone in this sub-threaD)
> The Sydney Opera House cost $102 million and
> was completed in 1973.
> The original plan was: a cost of $7 million and
> completion date of 26 January 1963.Only one video I've been able to find so far, makes the place look exceptional, although doesn't tell us much about the sound quality. [1] apologies for facebook source.
Regrettably it's sold out for the next 6+ months, and tickets are on resale in secondary markets for 10-50x their face values.
[1]: https://www.facebook.com/NDR.de/videos/1365568786826981/
> The cost to taxpayers climbed from an initially planned
> 77 million euros to 789 million euros ($835 million).
It had it's opening on 2016-01-11 and 2016-01-12. It's already had it's ticket system hacked (and fixed) and it's beautiful. [1] [2] [3][1]:https://i.redd.it/ybs5ba59yt4y.jpg
[2]:http://seasidemagazin.de/wp-content/uploads/elbphilharmonie_...
[3]:http://www.deutschlandfunk.de/media/thumbs/d/dbba6ff9beacb55...
Between these and retrospectives it's been possible for us to eliminate most all contra-productive meetings.
[0]: http://www.agile-ux.com/2009/01/09/return-on-time-invested-a...
Dev productivity killers:
* Notifications
* Meetings
* Emails
* Interruptions
Great managers block these. Bad managers cause them.
Otherwise, I can only agree with the advice about structure, and discipline. I'm currently shopping around for something like https://github.com/danger/danger to help me do my job better by policing Trello automatically - we've had great experiences using this for Capistrano's pull requests and I'd love to try this approach on Trello to police the rules we agreed to, but don't necessarily always follow. That'd probably save me double digit hours each week.[0]: https://twitter.com/_ericelliott/status/814082788378804224
> Be conservative in what you do, be liberal in what you accept from others
-- [0]: https://en.wikipedia.org/wiki/Manufacturing_Consent#Five_fil...
Edit: reading my message back I came off as impolite, sorry - genuinely curious, I've had the same breakage myself, and we started using Skype in lieu.
Neovim separated the client and server parts, and there are a host of clients (QT, HTML/Atom, etc) including the canonical one, from the docs:
When compiled with the |+clientserver| option, Vim can act as a command
server. It accepts messages from a client and executes them. At the same
time, Vim can function as a client and send commands to a Vim server.
https://neovim.io/doc/user/remote.htmlMaybe Kakoune does the same, I haven't checked. I also second the first child's note that being console based is a feature.
(ISBN-13: 978-0749953089) http://amzn.eu/8JHl1tw
I was replying to address two of the three points that these people invested 6 months to build YAPPM (Yet Another Proprietary Password Manager).
As is typical of developers they've solved a problem that _probably_ didn't need to be solved. With a more product orientated mindset a business plan, and some market research probably would have preceded six months of engineering effort.
The "more beautiful" is subjective, I'd argue that having only one platform targeted makes it much easier to build an app in-keeping with one platforms HCI guidelines. I happen to use a Mac, an Android phone, and a Linux desktop, thanks to WINE I can use 1Password everywhere, and knowing that the format is public, and documented, and there are 3rd party implementations I don't need to worry about AgileBits ceasing to exist.
I'm left seeing some developers making the same mistakes that I have made when building a product before finding out if the world really needs a _subtly_ different app to solve an already solved problem.
1Password also uses standard encryption, from the link [1]:
> We use Encrypt-then-MAC authenticated encryption everywhere we use encryption. The MAC is HMAC-SHA256 and encryption is AES-CBC using 256-bit keys. Key derivation is uses PBKDF2-HMAC-SHA512. More detail about these choices will be presented in the relevant sections on key derivation and item encryption.
> In this document we will refer to “blocks of data”. Unless otherwise stated, blocks are the length of AES blocks, 128 bits (16 bytes).
Edit: apparently Github lists [2] four libraries for reading OPVault, one each in Python, Haskell, Go and Ruby