beardedetim

Most players that use adaptive bit rate allow you to set it at a constant one instead, with the buffering and all.

I feel the same way and often click a specific rendition and then let it buffer locally.

> Democratic discourse fundamentally needs facts to debate, not lies, propaganda or un-verifiable anecdotes. People who come to a democratic discourse without facts deserve no time of democratic people.

I agree. Wholeheartedly. What falsehoods do you hold that keep you from participating in democracy then? Or are you saying that you, above everyone else, uses facts and logic only?

What have you voted for based on emotion?

Don't forget us little people on your way up

Because your api returns it as error.response.data while Joe's api might put it in a different key while Mike might put it as a different key.

If there's a way where we could say "this specific key will be this specific value in order to mean this specific scenario", I'd support that! But. Then. Isn't that the status that's I'm talking about?

I never said the error message can't or shouldn't be introspected and totally agree we should send our clients as much info as we can to make it clear on what they can do to fix any errors!

I just really really like being able to say "this specific field tells you, across all apis, what happened with this request" and don't see the gain in pushing that data into good luck finding out what key.

I don't want to introspect response bodies when I can introspect the status. If I'm given 429, I can automatically do something based on that. If I need to introspect the response body I have to say "okay, look inside Joe's api and look for key Foo. But in Sally's api, look for key Bar. And in Mike's api look for key Baz. And...."

I think its objectively worse that I, as the engineer, need to handle all of them differently when they all could have returned to me 429 instead and I could write a general wrapper for that.

Yes. Yes Yes yes. Status code is important beyond your eyes and your hand-rolled api interactions.

I can't believe the people here saying "fuck it, I always return 200"

The fact that I have to parse the body and intropsect its payload to know that the query is malformed is the worst client experience ever.

The company _is_ middle management. Those are the people being served by the company the most.

I see this as a feature and not a bug now that I no longer have an account on Twitter.

If I absolutely want to read a tweet, I can. But the barrier to entry is a _good_ thing to me.

I think Chattanooga, TN has 10g but not sure how expensive it is or how to get it. Chatt itself is pretty cheap in comparison to something like Nashville or bigger cities.

We use Bull at $CURRJOB and it works great until there's an issue and for _some reason_ jobs stall. Getting into the nitty gritty to debug the Lua code was not a fun week. We moved onto RMQ for our needs on the next project and are looking at ways the replace Bull/Redis in the old project.

> Then a tool is introduced that brings it all together.

I totally agree there and I think it's due to the fact that you've got a mental model of the problem space and your brain can see the empty hole. Once you have a tool of that shape, your brain knows where it goes and how it solves your problem.

Would we call that thin value betting on the river?

This is expressing something I've been trying to express for _years_. I've come to call it "throw away code" instead of "shitty code" because of what's happening in the comments: people always came back to me and said "Shitty code doesn't work!" and we get into an argument about what I mean by shitty code.

I find that throw-away code gets my point across much more cleanly without people's objections being raised immediately. Most engineers understand that when I say "throw-away code" it doesn't mean the code doesn't work. It just means that I can _throw it away_ when I need to later. It is "shitty code" because it's _supposed_ to be replaced.

If this is in the US and it's One Of Those States, I wouldn't be surprised if it was Flag Carying WW2 Nazis and not "cancel culture" ones. I grew up in One Of Those States and we talked highly about Slave Owners, Pinkerton, and other obviously bad people.

This. I think as I re-do my website, I'm adding my current salary next to my current position. Seems about the right thing to do.

I'd ask for specific, clear expectations and rubric from your direct manager. You should never ever ever ever be blind sided by your skip. If you are, the manager is failing you.

Could they instead have more than one set of employees? Maybe have people that only work 4 days a week but the business being open 7?

Let's say I have a list of friend objects:

myFriends: { name: string, friends: friend[] }[]

If I wanted to get a list of friends of friends, I could do something like

myFriends.map(prop('friends')).flatten()

Or

myFriends.flatMap(prop('friends'))

My data is a list of lists but I really want a list of friends so I flatten.

Maybe the Friend object is poorly created/designed but often times you'll just have to deal with whatever the API gives you.

Yup. If you call catch, you've handled the promise. You would need to throw from within the callback in order for the promise itself to reject after that.

Came to say this exact thing. HLS and it's fancy brother LLHLS aren't storage formats like MP4/FLV are. I think of HLS as a playback format: I'd play a Playlist when watching a VOD/livestream but I'd probably save it as an MP4.

Location: Tennessee, US

Remote: Only

Willing to Relocate: Not at this time

Technologies: Full stack JS/TS/Node, distributed systems/microservices, K8s, CI/CD, functional programming.

Resume: https://docs.google.com/document/d/1G2bL4Q6j4z8kbFXJYzquhvLg...

Email: timroberts@fastmail.org

Hello! I'm Tim and I'm a staff Software Engineer that's looking for an early stage/small startup where I can lead the engineering efforts towards quality while still shipping at speed. I've built MVPs/WAFLs, helped find PMF, and built both platform and user facing teams.

Like IndieLogin/IndieAuth?

I have (limited) experience scaling long-lived websocket connections and it _sucked_. It is _way_ easier to scale out little Node servers that are "stateless" than it is to ensure that Client A is connected to Socket A.

I would much rather scale out my REST/Graph/RPC API instead of having to scale out a WS API.

Yup, this is my thinking as well. If I go back to fully server side, it's because I can somehow instruct the browser to update without JS involved.

But you still need JS to update the DOM and handle the websocket stuff, right? Or is this all somehow done with JS disabled?

> distinguish based on whether it is in the interests of the recipient for them to be provided with certain input

Who would distinguish that? The receiver? The giver? Something/someone else? T

> Do Fisher Price and Disney “lure” children or do they just make products that are intended to be used by children?

If we change `lure` to `manipulate into wanting`, then yes I would say that. I would also expand this to _any_ marketing. I am currently wrestling with if I would go as far to say that _all communication_ is _manipulation_ but I feel that's a step too far for some reason while I definitely feel that _marketing_ is _manipulation_.

  Location: TN, USA
  Remote: yes
  Willing to relocate: no
  Technologies: React/Vue/A gular, Node/JS/TS, PSQL/Mongo/Redis, Docker/containers, K8s, Datadog/Jaeger/OpenTelemetry
  Résumé/CV:https://docs.google.com/document/d/1G2bL4Q6j4z8kbFXJYzquhvLgzcMYWj8vxKO7oAIoTy8/edit?usp=drivesdk
  Email: timroberts@fastmail.org 

Full stack engineer with a desire to build observable, accessible, stable software. Have many years of Front End development but am looking for more back end or full stack work instead.

> A big problem with CSS is that you end up making overrides no matter how composable you make the classes. And some simple things (e.g. responsiveness) are unintuitive and / or annoying to do in CSS.

10000% agree with this. I have found that copy/paste until you need to go back and change the same value a few times is worth its weight in salt with CSS. Never has "a poor abstraction is worse than duplicate code" been truer than in CSS.

What I found in my FE days ways that it wasn't until the project shipped and we were iterating on v2 did the actual reusable classes appear.