rymohr

It is all so wonderfully massive it makes one wonder what lurks in the darkness beyond the bounds of light.

You are confusing equality and equivalence.

It’s easy to do. Einstein did the same thing with E=mc2.

Equality is a matter of identity. Equivalence is a matter of behavior.

The speed of light is not an absolute constant as Einstein believed. C just represented the speed that light can travel as a relationship between energy and mass.

My favorite form of the equation is C equals the square root of energy divided by mass.

Behaviorally all that means is that as the energy to mass ratio goes up, the speed of light goes up. And as the mass to energy ratio goes up, the speed of light goes down. Hence time dilation, black holes, etc.

You seem to know a lot about this stuff. I have a question for you.

If fusion creates the potential for fission (radioactive waste) and radioactive waste can be used to build atomic bombs, how have we not figured out how to make mini perpetual-energy reactors?

Look into transcendental meditation, starting with this short overview by David Lynch: https://www.youtube.com/watch?v=z2UHLMVr4vg

I've been there. Please reach out to me on twitter (@rymohr) and don't throw in the towel just yet.

Not a bad writer at all. And I think all the problems you describe do exist. I'm just saying keep your head up and look too the bright side.

Be happy that you have a job that compensates you well, aligns with your values, is flexible to your personal needs, allows you to grow professionally, and enables you to reach for the goals you've set while you're here on earth.

And if that doesn't describe your job, please quit and come work with us or any other company that respects you as a human being first and a sysadmin second. Life's too short to do otherwise.

I hate when I see people throwing in the towel like this.

As a two developer company with four separate products doing nearly $500k in ARR collectively, Kumu [1] is a living example that it doesn’t have to be this way.

We rely heavily on bash, docker and cloudformation.

We only use Ubuntu LTS and we lag a release behind so there are plenty of tutorials available when it comes time to upgrade.

After experimenting with backbone, coffee script, flow, vue and multiple redux libraries we’ve settled on rewriting everything in typescript and developing our own thin redux abstraction.

Embrace new tech that makes developers’ lives easier while hopefully making things more secure too.

I get it if that’s not possible in large enterprise companies, but please don’t throw all software under the bus. Software is and will always be fun and there are still fun companies to work for if you’re willing to take a little risk.

[1] https://kumu.io

Yes they are very separate perspectives.

I’d argue they’re still viewing it from their own perspective, though one where they are attempting to circumvent security measures as an attacker.

I’m not talking about that kind of perspective shift. I’m talking about putting on the hat of a cold blooded killer intent on making as big a statement as possible.

Others seem to be commenting entirely from their own perspective. Try viewing this from the TSA’s or an attacker’s perspective instead and thinking about boundary layers.

In regard to the comments about disposing potentially hazardous water bottles, a TSA agent can rightfully assume that an attacker could dump the contents of said water bottle at any point before the security checkpoint, including into the public water supply. The fact they don’t attempt to prevent this from happening doesn’t make them full of shit, it actually saves tax payer dollars.

If enough people are interested I'm happy to do a webinar specifically for the HN crowd and do a deep dive on the technicals. Built on top of CouchDB and pretty neat stack overall.

Have you seen Kumu? https://kumu.io

It doesn't support standard UML diagrams but between sketch mode [1] [2] and icons [3] you may be pleasantly surprised. I personally use it to map out Kumu's own internal application structure and flows.

Full disclosure: I am the lead developer and cofounder of Kumu.

[1] https://www.youtube.com/watch?v=wX3kbCyOamQ (Gene Bellinger's intro to Kumu's sketch mode)

[2] https://www.youtube.com/watch?v=AFOz67co0yA (Benjamin Mosior sketching wardley maps in Kumu)

[3] https://docs.kumu.io/guides/icons.html (Kumu docs on Font Awesome support)

Any tricks for mobile?

They're like higher-order components on steroids that handle all the heavy lifting of the logic for the component (including what _should_ be rendered) but leave the actual rendering up to you (DOM structure, style, etc).

Here's a Vue example: https://banshee-ui.github.io/docs/guide/#why-banshee

There’s some work being done around renderless ui components but I’ve yet to see a complete framework.

Those were the naysayers’ words, not one of Ford’s justifications for the increase.

I recently started using a similar system but I went with now, soon, later, maybe. Once the maybes become nevers they go in the trash.

I write everything down on note cards which sit in a shoebox on my desk (with dividers for the categories above).

Assuming output is tied to hours. As we move away from industrial employment I'd expect that relationship to weaken.

Inflation would depend on the way labor responds. If folks continue to work the same number of hours, inflation is likely. But what if folks use the extra $1000/month to justify spending more time on non-income producing activities?

Or there’s an incentive for the unethical farmer to wreck twice as much to make up for the 50% decline in revenue.

Love John Gall's approach to systems. There's actually a section in Kumu's manifesto that quotes Gall's law:

    A complex system designed from scratch never works
    and cannot be patched up to make it work. You have
    to start over with a working simple system.

As an organic farmer I'm disturbed by how few commenters here understand what organic produce is.

"Certified organic" (aka USDA organic) means the farmer complied with a very strict list of regulations spelled out in the National Organic Program's Final Rule [1] and audited by an accredited certifying agent. See [2] for the TLDR version of the final rule.

"Organic" produce (aka non-certified organic) doesn't mean shit. The farmer may be following organic practices or may not be. YOU are the auditor in this case. Visit the farm and observe their practices with your own eyes before spending extra on this "organic" produce.

Bottom line: If you're concerned about synthetic fertilizers, GMOs, and/or sustainable agricultural practices in general, make sure you're buying USDA certified organic produce. Or grow the stuff yourself.

[1] https://www.ecfr.gov/cgi-bin/text-idx?c=ecfr&sid=3f34f4c22f9...

[2] https://www.ams.usda.gov/sites/default/files/media/Organic%2...

I’m curious how long the fallout would actually be an issue here, assuming trades were blowing 10-15 knots as usual.

If the visualization side isn't as important to you, Airtable is a great tool for managing structured relational data.

https://airtable.com/

Have you seen Kumu?

It's a general purpose property-graph editor, backed by a CSS-like language that allows you to transform and style your graphs.

- https://kumu.io

- https://docs.kumu.io/guides/views-advanced.html

(disclosure: cofounder / lead dev)

Surprised to see that your profile says "limited experience working with WebGL" when it looks like you clearly have your hands in deep.

Kumu | Senior Software Engineer | REMOTE | https://www.kumu.io

Bootstrapped data viz platform that helps people understand complex relationships, primarily through network, systems, and stakeholder maps.

We’re currently working with some of the world’s top organizations including The Omidyar Group, Gates Foundation, Hewlett Foundation, USAID, Stanford ChangeLabs, 100Kin10, Democracy Fund, World Bank, Humanity United and more.

    - Full-time remote position
    - Salary $60-80k
    - Equity 1-2%
    - ARR over $200k
    - Flexible hours within a small, mission-driven team
    - Annual adventure retreats
    - Stack: react, redux, rails, webgl, webpack/babel, aws, git/github, IE11+
    - Bonus points for experience with: graphs/networks, couchdb, elasticsearch, redis, d3

    - You’re a talented web developer (both frontend and backend)
    - You’ve mastered multiple programming languages and frameworks
    - You’ve built and maintained a complex library, single page web app, or product
    - You work well setting your own priorities and working with lots of freedom
    - You’re excited about (or at least don’t mind getting dragged into) snowboarding in Bend, rock climbing in Utah, surfing in Costa Rica, or whitewater rafting in Colorado.

If you’re interested, please send a SHORT email to careers@kumu.io telling us why you’re excited to work for Kumu. Experienced developers only. Lengthy and/or generic applications will be ignored. Thanks!

[1] https://twitter.com/rymohr

[2] https://twitter.com/_danprince

For anyone interested in applying this stuff to real world issues, I highly recommend the +Acumen Systems Practice course [1]. Rob Ricigliano and Karen Grattan have put together a solid, pragmatic guide on how to understand, analyze, and engage complex systems. We've been working with Rob and Karen at Kumu [2] for years now and nobody else comes close when it comes to applied systems thinking.

[1] http://plusacumen.org/courses/systems-practice/

[2] https://kumu.io

M3.medium instances are treated as current generation. M3.large, m3.xlarge, and m3.2xl instances are treated as previous generation.

Why? These other m3 instances are listed as current generation here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-...

Hi everyone, one of the Compass cofounders and developers here.

We're really excited to roll this out publicly but still a ways out. Happy to answer any questions.

If you're more interested in the technical side you might enjoy my post exploring single vs multi-tenant SAAS architectures [1]. Still not convinced single tenant is going to work but we're going to give it a shot.

Aloha!

[1] https://hackernoon.com/exploring-single-tenant-architectures...

Can't agree enough!

I actually wrote an article [1] last week exploring single-tenant SAAS architectures because I was annoyed with how complicated our multi-tenant plans were. Was bummed the HN post [2] didn't get any traction because I was really hoping for some critical feedback.

For me, the holy grail is a cost-effective system that doesn't back you into scaling issues down the road and is simple enough to be run by a single developer (on the side) rather than a dedicated team of sysadmins. Pipe dream? Maybe. But it's worth a shot.

[1] https://hackernoon.com/exploring-single-tenant-architectures...

[2] https://news.ycombinator.com/item?id=13385474