robertkluin

4 ms·

1.
by robertkluin 1y ago
Thank you! Very helpful feedback. We're thinking through better examples to try and highlight some of the key differences from other tools without it being too involved.
2.
by robertkluin 1y ago
Awesome feedback, thank you! The CLI is presently being reworked to expose that capability. Right now, you can use FunctionTest in order to validate that you get your expected outputs from an input. This works well because you can test many
3.
by robertkluin 1y ago
Honestly, Koreo can cover most of the use cases of the other tools just fine. We leverage Koreo to manage deployments of the Koreo controllers along with their service accounts and RBAC—it works quite well. We also use it with Helm in order
4.
by robertkluin 1y ago
I am not honestly familiar with Timoni, but glancing through the docs it looks like it heavily centered around Kubernetes deployments? Our initial use cases were centered around IaC for non-k8s workloads (think systems such as ECS or Cloud
5.
by robertkluin 1y ago
You should write your operator. You are correct: it is quite straightforward and you'll have solid understanding of what is happening and how it works. That is how this project started. We wrote custom operators for the various platfor
6.
by robertkluin 1y ago
I wrote the core engine behind this and your comment made me laugh pretty hard because I agree. I debated a lot about the best syntax and we experimented with various alternatives approaches. The core engine actually isn't YAML centri
7.
by robertkluin 1y ago
I maintain the core of Koreo. I'll hit the easy question first, then the more involved questions. Everything is in-code and designed to have a "proper" SDLC lifecycle—code reviews, approvals, merges. It is designed to be used
8.
by robertkluin 4y ago
Disclaimer: I’m currently building a product to help with my own organization challenges. This is what I realized as well—organization is the hard part. I kept struggling to find notes when I wanted to reference them. In my case, my notes a
9.
by robertkluin 5y ago
I routinely reference notes from several years ago in meetings. This was a decision we had a substantial amount of debate around internally. In the end we decided that a combination of person and timestamp tags combined with a robust search
10.
by robertkluin 5y ago
I work on Witful. We spend a lot of time and effort keeping the UI clean and refined; to the point that we have accidentally over-simplified in a few key spots. The result is that we've got a ton of hidden functionality. Things like co
11.
by robertkluin 6y ago
"We recently became aware of unauthorized access to certain of our information technology systems hosted by a third party cloud provider." Is this an attempt to shift blame? Using wording that implies it was someone else's fa
12.
by robertkluin 8y ago
Your experience sounds identical to my own. Particularly the "marketing book from the Neo4j folks" starting you down this journey.
13.
by robertkluin 8y ago
I have worked on a few projects where graph databases were used. I have not personally seen a case where I feel they add much value relative to their complexity and tradeoffs. One of the projects was a business workflow application centered
14.
More Environments Will Not Make Things Easier(blog.realkinetic.com)
3 points by robertkluin 8y ago|0 comments
15.
by robertkluin 9y ago
This has been a pain point for us with a couple of the language updates. Not as bad as other pre-1.0 languages I've used in the past (like Rust), but it has been painful. The compiler is helpful enough that upgrades are mostly just t
16.
by robertkluin 9y ago
I'm a partner at Real Kinetic. At Real Kinetic we've actually been internally using Elm for 2 years. While at Workiva, I OKed some internal projects to use Elm as well. Your observations are absolutely correct. We have actually fo