#dont see any matches and how the training scale and exercises are wrong and how they never talk abt defense and how they talk abt individua

[icecreamkink]

im very aware that when people rec sports media by saying things like 'you dont need to like sports at all!!' what it usually means is 'enjoying this sport will actively get in the way of liking this media' and its fine. ok. but like. People Who Self Proclaimedly Don't Like Sports

for fucks sake stop saying that ted lasso is Actually a good and competent coach bc he ✨ Cares ✨ . one, not enough and two. he is actually really fucking not; gonna put this under a cut and its kinda negative beware etc

yeah the premise of the show is 'haha american dude doesn't know what hes doing' i know, and football isnt the point, i know, but its. you have to admit at some point that ted lasso wants to have it both ways; it wants the haha what Is football and it wants to defend teds coaching style bc he is a kind person. bc he knows how to bring people out of their shell on a personal level. and thats great.  there is a discussion in the fandom whether caring abt winning is or isn't more important than caring for the people on the team in professional sports, or if ted is or isnt a good coach bc hes not v confrontational, and in my view these are not issues at all. however what everyone seemingly ignores is that-

ted is and continues to be for the entire show, HUGELY incompetent and ignorant, just, completely ignorant of anything regarding football, by his own constant admission, and he never cares to or bothers to learn. anything, at all. at any point. no, his kindness is NOT enough to make him a competent professional. no, his mental struggles dont explain why he is uninterested in doing his job. not only that, his disregard with understanding what the fuck it is hes doing at all is actually a pretty big hole in the 'caring' and even the 'underestimated' characterization of teds. like, people claim he's helping the athletes "on and off the field" but thats not true; he's only helping them off the field. ted does shit all to help them on the field, shit all, even his match choices, like benching jamie and starting with roy, are personal decisions thinking about them off the field. but a team of professionals and a club that employs dozens more people than ted lasso portrays depends on him and the narrative seems not to realize this. this is their livelihoods, not a footy camp for children. giving them books is great, but its not a substitute to knowing even the basics of whats at stake , like relegation, for example and i cant get over how many people found this blatant ignorance cute.

the fact that at episode 8 ted doesn't know what relegation is; that months into the job we're still having 'what is offside lollol' jokes; the fact that on the day richmond is going to play everton, he has no idea they haven't won against everton in decades, which means he hasnt reasearched everton at all. that only the day before a match against man city , only then teds gonna bother with gameplan strategies, meaning, again, he didnt research their oponent at all even though its a crucial game and man city is a technically much superior team that would demand careful tactic to beat; the fact he sees that nate, a kit man, has some tactical understanding and then just settles with relying on him alone, not even like, getting someone else to exchange ideas and train nate as a coach, just 'sure this'll do'. (there is also the fact that richmond is illogically understaffed and it bothers me like an itch, but like. its a show, alright, whatever)

these are jokes, yeah, but they're also ted being bad at his job. he has not done the minimum, really not even the bare minimim amount of research. he doesn't get familiar with the game, he doesn't understand positions, tactics, rules, plays, he doesn't know football history, he doesn't research the oponents, he doesn't even know how the league works! again, that's months into his position; the fact on the last episode of season one, after training Richmond for half a season, on the brink of relegation, ted is still fucking telling rebecca he doesn't know anything. as if he doesn't have not only the ability, opportunity but also the obligation of yknow. reasearching. getting informed. doing his job. care, since ppl love to talk about how much he cares. the idea that ted can care about the players as people while at the same time apparently not giving a fuck abt understanding what theyre all doing here is a huge, gaping logical hole in ted lasso's writing; before analyzing whether or not ted is a pushover, whether or not teds too passive, whether or not hes too non competitive, whether his positivity is good or bad, we have to ignore the fact this show actually tried to get away with 'nate and roy (both inexperienced too btw) take care of pesky game strategy, performance analysis, a team training and ted, the manager, only takes care of the players hearts <3' as if thats not only fair, but a good thing. he is utterly uninterested in half of his job, and that makes him a bad professional (and contradictingly selfish, too);   and 'oh football isnt the point' simply doesnt cut it for me. its lazy, and its annoying.

AND. for the record . i think ted lasso misses gigantic comedic and storytelling opportunities by doing this. teds clueless fish out of water self would be a lot more endearing and a lot more interesting and a lot funnier if it came up when hes researching his job, being interested in it, learning about it instead of being passively told these things and continuing to ignore them. rebecca being frustrated that her plan is shaking bc ted is willing to do the work and step up to his role would have been so much more effective than her being stumped bc hes just so aw shucks nice, period. they couldve shown that ted isnt just kind, but responsible, self aware, caring. it definitely would've helped with the show not feeling slimily 'usamericans come to teach meanie brits how to Lowve and to show how their outlook on life is Better' at times ( which was thankfully made more complicated in s2, but its still kind of there in the story tbh). there are endless hilarious football drama that they couldve used or brought up. there are so many storytelling opportunities to be found within matches. many more and more interesting contrasts as to how the popular sports in the us work vs how football works. football has an extremely unique relationship with people (in good and bad ways) and the show baaarely touches on that. like fucking hell we never even see the secondary characters that we assume are passionate so much as watch a match.

So. for the love of god. and i say all this as someone who did enjoy ted lasso, if mostly isolated episodes or storylines. stop saying ted is a good coach. he might be a good friend, a good influence, a good motivational speaker, tocador de pandeiro. a good pov character. but he is really not a good coach, much less a good manager, and thats a very valid criticism of the show

[faizrashis1995]

“Let’s use Kubernetes!” Now you have 8 problems

If you’re using Docker, the next natural step seems to be Kubernetes, aka K8s: that’s how you run things in production, right?

��Well, maybe. Solutions designed for 500 software engineers working on the same application are quite different than solutions for 50 software engineers. And both will be different from solutions designed for a team of 5.

 If you’re part of a small team, Kubernetes probably isn’t for you: it’s a lot of pain with very little benefits.

 Let’s see why.

 Everyone loves moving parts

Kubernetes has plenty of moving parts—concepts, subsystems, processes, machines, code—and that means plenty of problems.

 Multiple machines

Kubernetes is a distributed system: there’s a main machine that controls worker machines. Work is scheduled across different worker machines. Each machine then runs the work in containers.

 So already you’re talking about two machines or virtual machines just to get anything at all done. And that just gives you … one machine. If you’re going to scale (the whole point of the exercise) you need three or four or seventeen VMs.

 Lots and lots and lots of code

The Kubernetes code base as of early March 2020 has more than 580,000 lines of Go code. That’s actual code, it doesn’t count comments or blank lines, nor did I count vendored packages. A security review from 2019 described the code base as follows:

 “…the Kubernetes codebase has significant room for improvement. The codebase is large and complex, with large sections of code containing minimal documentation and numerous dependencies, including systems external to Kubernetes. There are many cases of logic re-implementation within the codebase which could be centralized into supporting libraries to reduce complexity, facilitate easier patching, and reduce the burden of documentation across disparate areas of the codebase.”

 This is no different than many large projects, to be fair, but all that code is something you need working if your application isn’t going to break.

 Architectural complexity, operational complexity, configuration complexity, and conceptual complexity

Kubernetes is a complex system with many different services, systems, and pieces.

 Before you can run a single application, you need the following highly-simplified architecture (original source in Kubernetes documentation):

   The concepts documentation in the K8s documentation includes many educational statements along these lines:

 In Kubernetes, an EndpointSlice contains references to a set of network endpoints. The EndpointSlice controller automatically creates EndpointSlices for a Kubernetes Service when a selector is specified. These EndpointSlices will include references to any Pods that match the Service selector. EndpointSlices group network endpoints together by unique Service and Port combinations.

 By default, EndpointSlices managed by the EndpointSlice controller will have no more than 100 endpoints each. Below this scale, EndpointSlices should map 1:1 with Endpoints and Services and have similar performance.

 I actually understand that, somewhat, but notice how many concepts are needed: EndpointSlice, Service, selector, Pod, Endpoint.

 And yes, much of the time you won’t need most of these features, but then much of the time you don’t need Kubernetes at all.

 Another random selection:

 By default, traffic sent to a ClusterIP or NodePort Service may be routed to any backend address for the Service. Since Kubernetes 1.7 it has been possible to route “external” traffic to the Pods running on the Node that received the traffic, but this is not supported for ClusterIP Services, and more complex topologies — such as routing zonally — have not been possible. The Service Topology feature resolves this by allowing the Service creator to define a policy for routing traffic based upon the Node labels for the originating and destination Nodes.

 Here’s what that security review I mentioned above had to say:

 “Kubernetes is a large system with significant operational complexity. The assessment team found configuration and deployment of Kubernetes to be non-trivial, with certain components having confusing default settings, missing operational controls, and implicitly defined security controls.”

 Development complexity

The more you buy in to Kubernetes, the harder it is to do normal development: you need all the different concepts (Pod, Deployment, Service, etc.) to run your code. So you need to spin up a complete K8s system just to test anything, via a VM or nested Docker containers.

 And since your application is much harder to run locally, development is harder, leading to a variety of solutions, from staging environments, to proxying a local process into the cluster (I wrote a tool for this a few years ago), to proxying a remote process onto your local machine…

 There are plenty of imperfect solutions to choose; the simplest and best solution is to not use Kubernetes.

 Microservices (are a bad idea)

A secondary problem is that since you have this system that allows you to run lots of services, it’s often tempting to write lots of services. This is a bad idea.

 Distributed applications are really hard to write correctly. Really. The more moving parts, the more these problems come in to play.

 Distributed applications are hard to debug. You need whole new categories of instrumentation and logging to getting understanding that isn’t quite as good as what you’d get from the logs of a monolithic application.

 Microservices are an organizational scaling technique: when you have 500 developers working on one live website, it makes sense to pay the cost of a large-scale distributed system if it means the developer teams can work independently. So you give each team of 5 developers a single microservice, and that team pretends the rest of the microservices are external services they can’t trust.

 If you’re a team of 5 and you have 20 microservices, and you don’t have a very compelling need for a distributed system, you’re doing it wrong. Instead of 5 people per service like the big company has, you have 0.25 people per service.

 But isn’t it useful?

Scaling

Kubernetes might be useful if you need to scale a lot. But let’s consider some alternatives:

 You can get cloud VMs with up to 416 vCPUs and 8TiB RAM, a scale I can only truly express with profanity. It’ll be expensive, yes, but it will also be simple.

You can scale many simple web applications quite trivially with services like Heroku.

This presumes, of course, that adding more workers will actually do you any good:

 Most applications don’t need to scale very much; some reasonable optimization will suffice.

Scaling for many web applications is typically bottlenecked by the database, not the web workers.

Reliability

More moving parts means more opportunity for error.

 The features Kubernetes provides for reliability (health checks, rolling deploys), can be implemented much more simply, or already built-in in many cases. For example, nginx can do health checks on worker processes, and you can use docker-autoheal or something similar to automatically restart those processes.

 And if what you care about is downtime, your first thought shouldn’t be “how do I reduce deployment downtime from 1 second to 1ms”, it should be “how can I ensure database schema changes don’t prevent rollback if I screw something up.”

 And if you want reliable web workers without a single machine as the point of failure, there are plenty of ways to do that that don’t involve Kubernetes.[Source]-https://pythonspeed.com/articles/dont-need-kubernetes/

Basic & Advanced

Kubernetes Certification

using cloud computing, AWS, Docker etc. in Mumbai. Advanced Containers Domain is used for 25 hours Kubernetes Training.

[wishi-wasbetter]

here i am again

in a way, it’s good that nobody here knows me or what my account used to be. nobody can see that not only did i fail, i went so badly wrong that i’m at the highest i’ve ever been.

i used to have a little side blog like this and write about my struggles, but that was before i even knew what struggle was. 

so, i’m going to get a lot off my chest right now, write what’s been happening, where i was before and where i’m at now.

i’m fat, let’s not avoid saying it. i’m not a girl thats 60kg and saying she’s fat because she wants to be 54. i’m more than double that. i’m 127kg today, although the precise amount is debatable because my scale can’t seem to decide exactly (i weigh myself 3 times to make sure, and it’s varying wildly between each, so i might need a new scale).

my previous highest weight was 99kg- i saw that number and i said, i will never get into triple digits. i fasted and restricted until i was down to 79. i entered a relationship, and became comfortable at 85. at this point, we went to europe together (somewhere i visit every time i can because i want to live there so bad) and i felt probably the happiest of my life. i was not skinny, no, but my body was capable, i fit into size 14 clothes so i could shop anywhere really, and i was usually able to overlook my tummy and thighs. photos from that time make me look so normal. i had a sharp jaw, i was not somebody to look at and say “oh my god she’s so fat”, i was just regular and content.

then my boyfriend and i moved in together, and for some reason i started binging when he wasn’t home. i’d wait until he left for work, and then a little longer to give him time to get on the train, and i’d leave immediately for the store. i’d buy food and eat it all before he got home, putting my rubbish in a bin outside. i went from 85 to 95, started feeling awful again. i was depressed, and that started my binging but binging also made it worse, it was a cycle. then my boyfriend left me in a very traumatic and sudden way, and this was the knock that held me down. from 95 to 109, to 112, to 119, to 125, to 128. i told myself 5 years ago i’d never see triple digits, and now i am well into those figures. i have to lose so much weight just to get back to my previous high weight, the last place i was so unhappy i had to change.

what is it about food, about eating, that makes me so out of control? even now, i can last a week just having one meal a day and start to finally feel like i am getting things under control, finally changing, finally going to get my life back, but then for some reason without thought i’ll binge. i dont think, i just do.

i need this to stand as record of where i am. i have ruined my life. i was happy, and i ruined it. now, my calves burn and ache when i walk just 3,000 steps. my whole body hurts. i have no energy, as soon as i wake up i want to go back to sleep. i have to contort to do up my shoes sometimes. regular stockings don’t fit me. i am unable to fit in a single thing i used to love, now i have 5 oversized items i wear and i can’t buy anything more because first, i hate everything plus sized, and second, buying more would be allowing myself to stay this weight.

i stay at home all day- i don’t want to be seen. my ex lives right near me and sometimes i see him, and have to try my hardest to avoid him, but he’s already now seen how fat i am now. i’m so ashamed. i just try to stay inside because i don’t want to be seen. i wear only black, i don’t dress up, i dyed my hair back to a normal colour because i don’t want anyone to look at me now. i have no sharp jaw, i have a real double chin, not just one that’s there when i look down, it’s now always there. stretch marks across my whole torso. on my upper arms. neck too fat to wear some necklaces now. i’ve ruined myself. maybe one day i can lose this weight but i wont be back to my own body, i can never have that again.

i’ve been to europe only once since i got fat. i found it easier to restrict, and i had so much reason to go out. i didnt want to be seen by anyone but i had to be out and exploring, so i did it. walking 17k-23k every single day, having very normal and healthy amounts to eat, i lost 10kg in the month i was there, i got down to 116. and then coming back here to my reality, i gained it all back so fast. here, there feels like no reason to go out, to move, to hope for something, to try.

and a year and a half after my break up, i’m still single. i have dated guys but it never ends well. in italy, i matched with a guy who took me on his vespa and then within 30 minutes made an excuse to drop me back home, then unmatched me straight away. i know this was because of my weight, know he had expected something better. since then, i can’t even bring myself to meet anyone. can’t handle that burning shame of rejection. i match with guys all the time but i can’t ever make myself agree to meeting up, i dont ever want to see disgust in somebody’s eyes again.

so here we go, we’re starting again. 300cal today so far, aiming for an 800cal day. tomorrow i’m buying a fitbit and i’m going to look for places i can walk that wont feel depressing and wont be near my home.

i’m 127 today, and my first goal is 119 by valentines day. that’s just over two weeks to lose 8kg which is difficult but it’s possible. if i’m doing what i am meant to do, i can make it happen. just by fasting for 4 days i can lose 6 of those kg anyway.

second goal is under 100 by may 11. losertown says i could be 97 by then if i eat 500 cal a day and do light exercise 1-3 times a week. i calculated and the most i could eat per day is 700cal to be 99, but i want to make extra sure i’m well under 100 so i’ll do 500.

third goal is back to 85, where i felt content. i don’t know what date i should put on this one, i think 27th july. that feels like a long time to be able to do just 15kg, so maybe by then i can be raising my calories slightly more to let it take just a little longer.

final goal is maybe around 65-70, where i think i will feel finally good about myself. i am pretty tall, so my goal should be a little higher than others, but we’ll see i suppose when i get there. i hope to god that time is before the end of this year, because i can’t stand another year of failure, of going backwards, of letting myself fester in this little self-dug hole that prevents me from having any life, any present or future and only being able to think of the past.