juiceandjuice
Joined 16 years ago
Joined 16 years ago
Now there is an equal metric regardless of the sex. Happy?
It's possible to have a nice, useable flat design. However, great care must be taken to use visual cues and be consistent in the UI. It's also possible to have high contrast. Low contrast is not flat design, it's a poor implementations of colors with a flat aesthetic.
Much of the flat aesthetic is rooted in swiss graphic poster design, however that doesn't translate so well to pages where dense text actually matters, especially with poor color choices. Much of designmodo's color scheme actually fails the contrast algorithm for small text, except at larger text it's generally okay. Bootstrap itself is pretty abysmal as far as this goes as well.
The flat aesthetic is nice, but those who continue on with it with disregard to contrast will not succeed. Accessibility and the flat aesthetic is possible, it takes more work and compromise, however.
I've written a few maven plugins that are just jython wrappers that import a few flags into the jython script (like the build directory) and then execute them. I've even written a generic python plugin that executes a script at a given path and imports any declared maven variables into it.
Sometimes it feels wrong, I know, but it's worth it.
I also wrote a new site plugin for myself that diffs between versions and throws all that up on a site for a auto changelog thing. It's useful for those rare "What the fuck did you do to the code in this release" occasions.
Following a general pattern is still a pattern. Patterns aren't as interesting as anti-patterns.
I'd sincerely suggest you reconsider looking into adjusting the quality of life in countries where high birth rate is actually a problem before telling someone how many babies they should or shouldn't have in a country with a fertility rate below replacement levels.
I'm horribly offended you would say such a thing to someone directly. It's not your body, it's not your business, and it's silly to assume she hasn't already considered something like this.
I love my Tektronix 2430A. I have some of the Tek 160 modules for the modular oscilloscope from the 50s, although I haven't really tried that. If you saw the guts, it's a point-to-point wiring masterpiece.
That being said, I have a few other issues with their wording as well. They should just say "we have a custom HMAC-based authentication scheme for our REST API". Also, it took me about 3 days to realize HMAC over SSL/TLS is about as secure and easy as you can get for most any language -- If you can send HTTP requests, you can probably do HMAC. You can add further safety by making expiring private keys for HMAC and other things, although my use cases are based on long running (weeklong+) batch computations, and not end users. (i.e. initial distribution of an expiring private key for HMAC over SSL, reauthentication schemes, etc...