kronin

8 ms·

31.
by kronin 7y ago
"Want some rye?" "'course ya do!"
32.
by kronin 8y ago
Db-per-service provides many benefits, albeit with some drawbacks. If you are going to adopt microservices, you've already had to accept most of the drawbacks. Trying to mitigate those drawbacks by consolidating will end up losing much
33.
by kronin 8y ago
If an architect that hasn't coded in 5 years or more dictates technological decisions to you, when they are out of touch of current best practices, how do you bridge that gap? Building codes change. Architects are required to design bu
34.
by kronin 8y ago
How can you design something that needs to be implemented in code if you yourself can't write code? If you can't produce in the trenches, what makes you qualified to dictate what those that are in the trenches are doing?
35.
by kronin 8y ago
Interesting examples. I have interviewed candidates who: * Have impressive products that they "designed and implemented. * Co-authored a book. * Founded and ran a {programming-language} user group. In all 3 cases, the candidates came a
36.
by kronin 8y ago
You handle the hypothetical by validating a new environment can be built and bootstrapped. Doing this on a regular basis, either by tearing down and rebuilding dev, or in a separate environment just for this purpose, is not a "nice to
37.
by kronin 8y ago
Trusting your private network is private turns that whole network into a candy store once a beach head in that network has been established. Defense in depth exists for a reason.
38.
by kronin 8y ago
The risk with having a reset mentality, "after all it's only dev" (edit: not intending to imply you said this), is that the opportunity to learn is lost. If they took the reset tack, then this occurred in production and they
39.
by kronin 8y ago
Another possibility is that they deploy feature branches in dev, so for a given service there are more versions running simultaneously.
40.
by kronin 8y ago
I tell the candidates that I will happily be their Google/stack overflow. Some candidates ask questions along that line, some don't. I agree that we don't code in a vacuum. What I'm trying to ascertain in the interview i
41.
by kronin 8y ago
I agree about your unspoken assumption, but many interviewees ask. And the post I was responding to pointed to the Apache commons library, so I hazard to say it's not universally known. A fail is not a red flag. A senior candidate not
42.
by kronin 8y ago
> There is a way to weed out the liars - you hire them and then when it does not work out you fire them. In my experience, firing someone takes multiple months. Months in which they are mutating the codebase (with review, but it's a
43.
by kronin 8y ago
My interview covers coding, data structures, algorithms, system design and data modeling. I attempt to tailor to the candidate, but there needs to be some level of standardization to be able to justify to the recruiters why a candidate didn
44.
by kronin 8y ago
Since you're attacking me, do you have any experience screening resumes? Phone screens? In-person interviews? Have you had the experience of a candidate that has apparently "done it all" on their resume, and confirmed their s
45.
by kronin 8y ago
I asked a candidate to implement an algorithm that reverses a string. I don't see that as a complicated problem. It's literally a for loop, and based on how they choose to implement it you can ask about implications of append vs.
46.
by kronin 8y ago
It's the start of the coding interview. It moves on from there. This candidate didn't even ask if he could use Apache commons, and I hadn't yet specified that he couldn't use a 3rd party library. So yes. He failed on man
47.
by kronin 8y ago
I give them a chance to judge their own skillset. After looking at their resume, I have an idea based on the projects they take credit for, what their experience level should be. If what they state lines up with their resume, and they are u
48.
by kronin 8y ago
I've interviewed and been interviewing for over a decade. I have had the displeasure of interviewing many people who have very impressive resumes yet when asked how they would judge their skillset in an area, and being told from them t
49.
by kronin 8y ago
No, I was answering the statement "it looks like an absolute nightmare to debug". Amazon's page request and rendering pipeline, I would estimate, is necessary complexity. Due to the large engineering force and the speed at wh
50.
by kronin 8y ago
Amazon has invested significantly in tooling that makes debugging this possible. I would not recommend anyone go down this route unless they are also willing to invest heavily in the tooling support necessary.
51.
by kronin 8y ago
The ports that are common are the envoy ports. In the roadmap it's mentioned that support for istio mixer is planned implying that mixer isn't supported now which, if it was istio, it would be.
52.
Running Apache Cassandra on Kubernetes with an Operator(opensource.com)
1 points by kronin 8y ago|0 comments
53.
by kronin 8y ago
Thanks for this. "Unlimited tolerance must lead to the disappearance of tolerance." It seems to hinge on "rational argument" to base determination on whether tolerance is warranted, lest intolerance creep in. I wasn&#x27
54.
by kronin 8y ago
"tolerant of intolerance"... Interesting concept. Who defines the intolerance?
55.
by kronin 8y ago
"tolerance" swings both ways. Unless you choose to be intolerant. The majority of people who spout tolerance and acceptance at me are the least tolerant and acceptant of other beliefs.
56.
by kronin 8y ago
Agreed re: both of these wins. On the security front, would be ideal if these resulting containers ran as non-root. Hopefully that will come soon.
57.
by kronin 8y ago
Spring boot microservices using liquibase as schema evolver, we are using helm hooks to run a job pre-deploy that leverages a spring boot profile which runs the evolutions. If it fails, return non-zero exit code and the deploy doesn't
58.
by kronin 8y ago
1,000x this. A simple refactor commit, with a comment stating "reformat to match current coding standards. No functional changes".
59.
by kronin 8y ago
Repos. Watch the Kelsey Hightower keynote video I added to my post. Don't get me wrong, I think auto devops is a good thing, but it's most certainly not gitops.
60.
by kronin 8y ago
Please don't. I am using gitlab, though we quickly grew beyond auto devops. Your definition of auto devops is different than gitops. Gitops is the practice of using commits and pull requests to execute change and do releases. Weave use

More ›