yebyen

56 ms·

481.
by yebyen 7y ago
Rio is a wrapper around Knative and Istio, from what I can tell. The thing I don't see (and I haven't tried Rio, so maybe someone who is using it can say this better) how does it build your apps? Because it wraps Knative, I can
482.
by yebyen 7y ago
The best suggestion I've heard recently is, when someone writes a flaky test, that person needs to be the one who fixes it. (If you write flaky tests and I fix them, I learn how to not write flaky tests, and you keep on writing them,
483.
by yebyen 7y ago
I've worked three different places where I attempted to implement automated testing strategies, failed twice and succeeded once. If you subscribe to the anecdata model of knowing things, here goes: In the first company, there was a st
484.
by yebyen 7y ago
Wow, this blew up! Thanks for all the information! I've used sequel before and agree, it's closer to the SQL and does the job well. ROM looks excellent. I'm just reading down the page you linked, and I love every word. I
485.
by yebyen 7y ago
If you can call it that... my site is actually a Jekyll blog, in development mode, this is running in the most needlessly Ruby way. (A production deployment would have pre-rendered all the pages, and there wouldn't be a need to have a
486.
by yebyen 7y ago
Yes, it's there, you can enable it, but I haven't heard anyone recommend it for production use, and it's not enabled by default. I tested it myself, it seemed to make my boring use case a little bit faster, once the JIT cach
487.
by yebyen 7y ago
100% agree. Developer happiness, conceptual compression is another important concept that DHH likes to talk about. If there's a hard topic that devs need to understand sometimes, Rails makes it a point to guarantee that devs don&#x27
488.
by yebyen 7y ago
Ruby 3x3 is a thing (make Ruby 3.0, 3x faster), and Ruby 2.6 is said to include an optional JIT compilation mode. I haven't seen any benchmarks or analysis that say JIT is ready for production use, but indications are strong that the n
489.
by yebyen 7y ago
There are also cases that are less justified that you might have, especially once you start going down the road of "my dev environment should be a clone of production" If you have an Employee model and it returns certain attribute
490.
by yebyen 7y ago
I prefer to say, merges should only flow one way. (And always rebase before a merge.) If you are merging master into a feature branch that has ongoing work and continues without merging back to master, that's the problem. If your feat
491.
by yebyen 7y ago
Estimates for internal client is a different ballgame than estimates for sales, it would seem. My approach to the same project would be different if I know that I get to walk away when the project is over, versus if I know I'll be the
492.
by yebyen 7y ago
To clarify why this strategy is not as bad or egregious as it seems, one must only ask: what are the consequences of overestimated time for work (that gets delivered early?) And what are the consequences of underestimating work? Would you r
493.
by yebyen 7y ago
> we always include time for writing automated tests in our estimates. It can slow down initial development, but it greatly improves the efficiency of operating and maintaining a software system. It isn’t until a system grows that you tr
494.
by yebyen 7y ago
The distinction makes important fault domains and whose data centers. If you are a Comcast customer and your internet goes down, and Netflix is unavailable, who do you complain at? If you're smart enough to notice that both are down,
495.
by yebyen 7y ago
I'd buy that argument. It jibes well with the research we did to come to this conclusion, when we started buying numbers in local area codes at the call center I used to work for... (excerpt from where I posted it elsewhere) > In h
496.
by yebyen 7y ago
You're right. On two counts. My folks live in a small town in Western NY and everyone has the same exchange. I have to believe that's a minority of people by the numbers, but I could easily be wrong, and if rural towns are spec
497.
by yebyen 7y ago
70% of the spam calls I get could be stopped simply by blocking the exact same exchange that my number is in. Do spam callers really think I'm expecting a call from the same area code, same exchange as my own number? Do most people ha
498.
by yebyen 7y ago
> If anything, easy containerization negates one of Go's strongest selling points (i.e. standalone executables with no need for a runtime environment). I don't know about that, I think that is still a strong selling point for G
499.
by yebyen 7y ago
I actually wrote this for you, before you wrote your post: Create a set of focused how-to guides for building a Kubernetes + Workflow + cert-manager + nginx-ingress cluster, that you can run your blog or anything else on. This can be a tuto
500.
by yebyen 7y ago
I don't know when your testing occurred, but I heard that long ago, AKS was very slow to provision and that it had gotten better. I have one AKS cluster that is pretty lightweight, does not get torn down or re-provisioned often (so I
501.
by yebyen 7y ago
I will say that once in my whole time using AKS, the nginx-ingress addon failed me in a way that caused my cluster to stop serving traffic. I contacted my friend at Azure (my cluster is not high-stakes production) and learned that they were
502.
by yebyen 7y ago
This looks like a great article and not highly specific to Azure. It is a tutorial for Azure AKS, sure, but while you do use AKS for the cluster management and Azure services for a few things like DNS, you've taken us all the way thro
503.
by yebyen 7y ago
I guess we're pretty lax about it and not really following the rules. Almost always people do not respect the rules of the stand-up, and it becomes the status report meeting. If you're doing it correctly, it should definitely not
504.
by yebyen 7y ago
5 minutes for 7 people? Something is wrong with your math, you might get the meeting over with in 5 minutes on the best day, but it won't have been very valuable or informative. How exactly are you supposed to make three whole stateme
505.
by yebyen 7y ago
That's exactly what it's for. To put a finer point on it, a daily stand-up meeting should be no more than 15 minutes long, and about three specific things. Each person should talk about exactly these three things (or less, if you
506.
by yebyen 7y ago
Awesome, that also sounds good The big advantage of the job DSL plugin is that if you have many similar repos, you don't just treat them all the same with multiple copies of the same Jenkinsfile, you actually can build the jobs from th
507.
by yebyen 7y ago
Have you used the Jenkins Job DSL plugin? I'm just getting started using it, but it seems like the solution to scaling up to a lot of Jenkins jobs. There's a good talk about it, and since you're one of only two people in the
508.
by yebyen 8y ago
I for one am glad to hear this aired in a public forum, even though it took several pointless replies to get to the "hey, check out this bad default setting"... I'm learning Python as a distant third priority, I had only hear
509.
by yebyen 8y ago
You're not wrong, as far as I can tell. I'm a rails dev who has some godawful vanilla JS and JQuery in my legacy apps, that I maintain to some extent. We've largely avoided the quagmire of component-ized frameworks like Reac
510.
by yebyen 8y ago
If the interface is so wrong that the implementers actually can't use it safely, that's not a microservices problem any more than it's a monolithic architecture problem. It's important to design interfaces before they ar

More ›