You Need Kubernetes? 

Almost every technology in my CV.

Lol this is so accurate 😂

Typical frontend developer requirement on LinkedIn. Yes, frontend

My app does, but yeah most probably don’t. When users eventually find my pomodoro app I’ll be able to scale like crazy.

​@@Kane0123lmao

Lollll

yes though I am wondering the difference between next js and sveltekit . I am liking sveltekit so far but I don't know.

This is how business really works. 100%. I never use fast to ship frameworks

Management giving two sprints is being so generous

that's me in my current freelancer job

Well said.

k8s work until some architect has the bright idea to use all the toolbox of x provider, I mean, to move between cloud providers.

​@@GokuMercenarioSCyes you have to to keep using standard and open source tech or the vendor lock-in can be very hard

This is the best, most concise explanation of k8s I've ever seen

You should get hired as a lead marketer because that was the clearest, most concise and most sellable way of describing K8s.

Why not just containerize your application(s) and deploy on heroku, cloud run, cloud foundry etc? Then when/if you use k8s or nomad then do that when you need to?

exactlyyyy

I’m 2 dawg can’t figure out DP 😢😢😢

The case I remember recursion is a directory listing. Perhaps gathering file names and sizes, and calculating folder sizes.

fibonnaci sequence + memoized is how I figured out recursion better. but I will say, I have used recursion in the wild for bread crumbing on a website. it was kinda sus.

@@mr.mirror1213bro why is this true. I can’t figure out dp, so I use recursion with memoization on leetcode

Recursion always winds you up reading a Stack Overflow post.

I tried HTMX yesterday for the first time. It's pretty good, but I would not know how to structure a large app with it (do I create a new .html file for the stuff I want to have old html swapped with?), or how to persist some client states that I need on the client side. I would probably have to put everything into DB, no idea.

@@SandraWantsCoke All depends what rendering framework you use. Some can use partials (fragments of html in the same .html file).

Using JStachio which is fully compatible with Mustache. It compiles templates at compile time and can have no runtime dependency. It has partials and fragments. For example, the main parts of a dashboard are in their own html file which contains many fragments to enable swapping out html within the larger component. It works extremely well. As the templates are strongly typed and compiled, you see errors in the IDE (intellij), which has been truly awesome.

Sounds like your websites weren’t interactive and shouldn’t have been using react/angular over a static site generator

Not sure why you jumped from php/jquery to react in the first place

Maybe it would be even more appropriate to say that introducing recursion isn’t hard.

it depends. it's probably the side effects that make debugging recursion hard. i think that recursion which only builds a return value (an expression) requires less debugging, because it's easier to reason about

​@@AG-ur1lj "Changing some value until some condition is met" changing stuff is pretty much a side effect, so yeah that's trickier to reason about but it's not because of recursion. you can make recursion look just like a loop if you pass on to the next call, what you would pass on to the next loop iteration. so it's not necessarily harder to reason about. but i get that syntax wise it would require creating a whole new function (i know that feeling in most languages). in functional programming languages you get away with this, because the syntax for creating a recursive function is about as heavy as writing a loop (only slightly heavier). loops are only a subset of what you can do with recursion. typically it's problems that work with trees that are easier with recursion. but lots of things are trees. like finding an employee's highest level manager by going through the manager's manager etc, or problems like adding 1 to every node in a tree. XML is also an example of a tree. but even in functional programming people try avoid dropping to recursion: most things, can be done with just a function call, because function definitions are values an so can be passed in and returned as values like in JavaScript (a.k.a. Higher Order functions). but also because a function call with missing parameters, results in a new function that expects the missing parameters (a.k.a. Lambda Calculus). so you get a lot of one liners like in this video. side effects (including global mutable state) are typically avoided in functional programming. you still need them to change the outside world, but they are typically confined to only a few parts of your program, and make the rest easier to reason about. bugs can still occur of course in functional programming, but a strict type system and the increased simplicity of the code makes it less likely (the whole program is basically 1 expression instead a statement like in most other Imperative programming languages). TLDR: basically it helps if the language is flexible enough to not have to write out recursion, every time you need it.

@@AG-ur1lj "Changing some value until some condition is met" changing stuff is pretty much a side effect, so yeah that's trickier to reason about but it's not because of recursion. you can make recursion look just like a loop if you pass on to the next call, what you would pass on to the next loop iteration. so it's not necessarily harder to reason about. but i get that syntax wise it would require creating a whole new function (i know that feeling in most languages). in functional programming languages you get away with this, because the syntax for creating a recursive function is about as heavy as writing a loop (only slightly heavier). loops are only a subset of what you can do with recursion. typically it's problems that work with trees that are easier with recursion. but lots of things are trees. like finding an employee's highest level manager by going through the manager's manager etc, or problems like adding 1 to every node in a tree. XML is also an example of a tree. but even in functional programming people try avoid dropping to recursion: most things, can be done with just a function call, because function definitions are values an so can be passed in and returned as values like in JavaScript (aka Higher Order functions). but also because a function call with missing parameters, results in a new function that expects the missing parameters (aka Lambda Calculus). so you get a lot of one liners like in this video. side effects (including global mutable state) are typically avoided in functional programming. you still need them to change the outside world, but they are typically confined to only a few parts of your program, and make the rest easier to reason about. bugs can still occur of course in functional programming, but a strict type system and the increased simplicity of the code makes it less likely (the whole program is basically 1 expression instead a statement like in most other Imperative programming languages). TLDR: basically it helps if the language is flexible enough to not have to write out recursion, every time you need it.

It's tradeoffs all the way down.

At the pareto frontier there is no such thing as best. Only better at the expense of something else.

It depends ON WHAT, though?

Attorney Tom the software developer: "it depends"

My job uses k8s. The k8s engineers claim that ecs sucks Not sure how valid that claim is. The apps we run are simple and personally I think k8s is overkill and you have to spend so much time maintaining the cluster too

​@@asdasddas100 I worked for one of the biggest telecoms, which runs most products on AWS ECS. It always depends on the prerequisites, i.e. what "sucks" and what tradeoff you choose.

And I'm sure that Telecom company had an massive infrastructure team that built the whole system of deploying shit to ECS. Whereas you can handle k8s alone.

@@Sadzeih 3 teams, ~15-20 people. Currently they merge similar solutions across globe so probably more now. By handling k8s alone do you mean ready-to-go products like AWS EKS or Azure AKS? Maintaining the k8s platform built from scratch is the work of over 50 people. It took 3 years and 500+ people to build a platform on top of k8s in a bank I worked for. In the case of ready-made k8s, this should be a lower bar, but I have never used such solutions so far.

Yeah. There's basically 0 reason to use non-managed k8s these days. GKE or EKS are great.

GOTTEM

It's very simple compared to a lot of other software. Takes about a week to understand the majority of the use cases. Takes years to know the edge cases.

What other softwares?? ​@@doceddie

I can't help but read Wayland and always hear Sean Bean reminding me that we ought to be off to Weyland Priory. (I know its actually Weynon Priory)

@@MagnumCarta I'm in that awkward age where it's hard not to associate him with Boromir because I was just barely too young to know all his great roles in the 90s.

Unless you’re on nvidia lol

I don't follow. You're doing the work to deploy to a large number of users while hiding it from management? To subvert their decisions I presume.

Thank you, saved my time x))

Sorry he doesn’t just regurgitate easy info.. you’re very new and don’t understand he’s discussing theory not simple yes no answers to spoon feed you

​@@codegate615is this bait or have you got a termite up your ass? You're coming off really aggressive

But when my simple to-do app blows up I’ll be ready.

Even Docker Compose can handle that if you haven't forget about HEALTHCHECK in the image.

@@chupasaurusif you are at the level where you can handle it with docker compose then just running k8s locally and using it instead is not really more effort.

@@mudi2000a Compose has service update policies since forever. Sure it lacks proper networking to run multiple instances of the same service, but that's where service discovery comes handy (wink-wink Consul/Vault). And Ops pain to run it is tiny bit worse than to have a managed k8s cluster, on-premise ones are orders of magnitude worse.

@@chupasaurus I love my home k3s cluster which makes it easy to host my own apps in a cluster and manage ingress etc. just like running the AKS stuff at work more or less...

@@chupasaurus k3s and rke2 have been pretty easy to deploy for me vs docker compose tbh.

If you're starting green field and building it all from scratch I sort of agree, but when dealing with complexities of existing products/features that have to be maintained or migrated it can very easily turn any almost number you care to give either wildly optimistic or wildly conservative, usually experience hedges towards conservative estimates of time required in these cases.

Seniority is having the spine to explain to the boss that their business rules come second to the release of the finished product. And that the only way to get them in the estimation is to remove the estimation from the purview indefinitely

Your average dev does not really need to know how tcp works 😮

TCP was a lot of fun to learn about in my mobile and wireless computer networks course in university. Since mobile communication is affected by attenuation, a direct line to the end server is really bad because of TCP's congestion threshold algorithms. One solution is to set up two channels, one between the client and a mobile base-switching station (that takes in traffic from cell towers) and from the mobile base-switching station to the end server. The base-switching station is not affected by attenuation since it often uses direct physical lines between providers. The end server's intermediate nodes in the network never throttle the connection since it remains stable from the base-switching station.

Syn-Ack brother.

Wow, it’s rare for a SDE to know what TCP is?

we learned to write a tcp ip stack in high school, but that was back in 90ies. I am sure things have changed too lol

Yes, but at the same time you remove dependency hell by separating environments in application containers and allows for the automation of said containers. The alternative is doing that manually, which can be seen as insanity sometimes

Was it worth getting the CKA, I've done the CKAD exam a couple years ago

@@dandogamerIt is worth it. You get to learn the in depth of what does manage a k8s cluster means, so 100% worth it

Didn't know that, but do know the saying has been long since debunked as casuistry.

I just want to let you know that when I read "missile proving grounds", I immediately pictured two missiles in medieval armor rocking themselves vertically across a field chanting about their reasons for fighting this day upon these hallowed grounds.

no what the fuck? it comes from Cicero and it means what it says

Chat jippity explained it to me stating that the common use of the phrase is misusing it and a more correct usage would be a statement like “parking allowed on Sundays” is an exception to an overarching rule that shows the existence of said overarching rule (that parking is not allowed on other days). But it also explained that 1) it comes from a Latin phrase that roughly translates to “the exception confirms the rule in cases not excepted” (exceptio probat regulam in casibus non exceptis) and also that, yes, prove isn’t meant in the meaning of “shows evidence for” but in the old meaning of “tests” just like how proving grounds means testing grounds.

Wikipedia (best source ever) says it's disputed and noone really agrees, but this would certainly make more sense. Although usually when I find words or proverbs like this, I usually stop using them because they aren't useful for communication.

Practical note: Python has a stack depth limit, so recursion on an unknown depth is a bad idea. IIRC it's also slower than using a loop. I love recursive code though. So clean.

“wishful thinking” as my prof calls it is one of the biggest roadblocks but it’s not the end. there’s many more afterwards.

Hehehehe

The whole `sysadmin vs developers` and `DevOps` deal is the ops guy cursing the dev guy for breaking prod at 3am. Devs just don't care as long the can deliver faster and close user stories