_fullpint

What a weird thing to say. This is about the Kentucky Derby, the mint julep is synonymous with the derby. And while that is possibly how they’re done in New Orleans, it’s absolutely not how it is done in Louisville.

Going back through Discrete would probably be a good idea as well.

You're just "trivializing an incredibly complex moral conundrum" -- by stating someone is "co-opting someone's pain for your own political or ethical brownie points" for having an opposing view point on " an incredibly complex moral conundrum."

Given the rest of what you have written in this thread, your idea of justice comes off as being based in a punitive approach, and it shouldn't be surprising not everyone agrees with that.

Is this Three Blue One Brown?

One, the lack of support for HKT isn’t great. There are some work arounds, but they aren’t particularly safe and end up being pretty cumbersome to implement.

Another big one is while the language supports lambdas and closures, it’s highly recommended to not perform any currying.

The lack of HKT is the only disappointing thing about the lang for me.

There are some ways to get around it, by simulation and using ‘as’ but it isn’t particularly safe.

I write a lot of Rust these days and unfortunately really great FP stuff is pretty damn cumbersome to write.

It indeed does

Not too sure how pushing scooters out of the way to remove barriers for people who cannot go around them is "antisocial." Especially when those people are neighbors and are in need.

The companies and their users -- the companies don't have structures to prevent their users from leaving their property in right of way, their users leave the companies' property in the spaces preventing those in need of using the space -- are the ones partaking in antisocial behavior.

> the battle here is not to fight over who has the right to be on the 10% of the street we call the sidewalk

I'm not asking for 10% of the sidewalk for myself -- that's ~4.8 inches, which is much less of the space needed for a stroller, a person with a cane, or someone in a wheelchair.

I don't see any lobbying, let alone any actions from these companies that ensure that the quality of the lives of the people I mentioned isn't negatively impacted. What I do see is rent seeking and extraction of public value for there own profits.

Lobbying is great, but they aren't doing anything currently to actually curb their users from partaking in reducing the use of public space for those that can't simply 'walk around it and pray their lobbying works one day.'

This grind my gears so fucking much! You are running your business not only on property that isn't yours, but the public's -- AND it's an inconvenience to every person who walks by in a busy neighborhood, some that absolutely need the sidewalk.

To be honest -- when I see this, I also go out of my way to say something. I don't have a hate for scooters, I just get really annoyed by the lack of perspective people have for their neighbors.

With that said, I rarely have to say something about this to the people in my neighborhood, because while they may be blocking the sidewalk to do whatever they may be doing, they are incredibly aware and say something as you're walking by:

"sorry about my car"

"sorry about my trailer"

And I know that if someone was/is in need they'd go out of their way to help you out.

My complaint wasn't about my neighbors -- it's a pretty tight knit community. It was about everyone who comes in for some event/holiday who doesn't give a shit about those of us who live here. I'm personally not inconvenienced by the scooters, I just care about my neighbors that are.

> Why don’t you take 2 minutes and push them to the side of the sidewalk if you care so much about ADA access? You can fix the problem you are encountering, and the people you want to protect CANT. You are choosing to make the problem worse for them? Why?

Uh... I said out of the way. I push them onto the easement required by the city which is grass from the curb to the sidewalk.

There is no way that this is in any way "worse." Especially due to the fact that they are usually in the way via being not parallel.

Absolutely hate these scooters from an ADA prospective.

My neighborhood is a mostly quiet one near the center of a large city, where there are a lot of mothers who push their kids in strollers, older folks with canes, and some people even in wheelchairs.

On the weekends -- sometimes the weekdays as well depending on the time of the year -- the city gets flooded with both tourists, and suburbanites who want to go to all the 'trendy' spots often opting to use these scooters.

More often than not they park them right in the middle of the sidewalk. The side walk that the strollers, canes and wheelchairs use on a daily basis. Usually when I see this, I just knock the things over and push them out of the way.

Isn't this what a homotopy category is for though?

Only has to be at the root.

>> What isn't a footgun in the terms that you declared?

There are definite degrees to this. But something like FP that declares f(x: X) => Y, instead of something like OOP where given context: x: X, y: Y and f() => void (where there is an effect on y) those are massively different scopes of problems.

It's not that you cannot do the previous in the latter, but that people -- especially those that are inexperienced and haven't dealt with the hell of a stateful programming -- routinely reach for as a solution to their problem.

>> I believe people dislike OOP because the vast majority of code is written using OOP.

Why do you believe that's the reason why? There's no implication here -- just a genuine curiosity as to how that was the conclusion.

>> If everything were written using data oriented programming or whatever, people would have the same reaction as they have regarding OOP.

DOP especially given one with a static language forces you to move from one type to your next to solve your problem, and handle your edge cases.

From experience DOP and FP can be intimidating, but usually end up being easier, and the development time, along with the time to stability are hugely reduced -- because it's inherently dumb.

Sure your first proposition is true. But many people realize you more than likely will not have a team of good to great programmers.

OOP is a massive foot gun for many programmers who are okay at best. And that effect is exponential as the project and their team grows.

I’m not particularly familiar with CRDTs but it sounds like you’d need to define a semigroup no?

I had a pretty bad Triplebyte experience myself.

Scheduled a practice interview and the only slot available was ~6AM my time. Nobody showed up and I wasn't informed that they wouldn't be showing up.

After reaching out about it -- they tried to tell me that my interview scored poorly, and that I would need to retry again in a few months. After some back-and-forth they realized both that it was practice interview and that the person didn't show up. So they rescheduled the practice interview.

When the interview did happen -- this was for ML stuff -- the interviewer was just no great. We spent so much time discussing the differences in terms we used -- mine largely coming from University, there's from I'm assuming their formal education -- that much of the interview was wasted. It literally came down to me deriving what we were not agreeing on for them to understand we were talking about the exact same thing.

I then had to reach out several times for my results, I'm assuming due to the fact that you're allotted one practice interview, and technically I had two(?). When I finally got my results I was again informed that my results were not good enough, and I'd need to wait to reapply. I gently informed them that it was practice interview, and the representative apologized their mistake.

When I reviewed my results... the interviewer didn't rate me too well, largely due to our differences in terminology. They also didn't like my coding style -- even though no one has ever complained to me before -- and rated the coding exercise poorly even though I was able to perform what was asked of me.

I just gave up.

Then several months later, I got an email about being TripleByte certified or whatever.

The whole thing was a really bizarre experience.

The lack of understanding of the downfalls and conflicts with facial recognition with justice system and this post is every reason why it shouldn’t be near the justice system.

Or running the pasted scripts through bash in fish?

I actually use this guy: https://github.com/edc/bass

Oh man! Domain knowledge is absolutely HUGE. I cannot even begin to tell you how much I've had to dive into literature on topics well outside of my domain to begin to understand how to use my outside perspective to come up with solutions.

Respecting stakeholders, and being able to be humble about asking for help understanding the domain is paramount.

Somethings don’t log correctly if you use the built in interpolation without using JSON.stringify. And if you use stringify it’ll actually “freeze” it and it will not be interactive.

It’d be neat if you could extend this to Windows Terminal as well. They both use very similar structures for themes.

Check out io-ts — it can take a minute if you’re not familiar with functional programming, it’s built on top of fp-ts.

Being able to encode/decode IO safely has been a huge blessing when working with JSON.

I don’t know about that being such an absolute. Personally, I feel pretty connected with people just being around them even if we aren’t interacting directly with one another.

It’s also fairly easy when living in a big city to know your neighborhood well enough that if you don’t want to be alone you can expect to run into one or two of a certain few people at different locations.

Like I know of I got to x,y,z coffee shop I can run into acquaintances of set X, Y, Z. If I want to grab a night cap at bar a,b,c I am run in to set A, B, C. And if I just want to be alone I can just wave and say hi.

There's a decent case for using anomaly detection in an attempt to solve some zero day attacks. The idea of not knowing what you don't know, can be used in such scenarios. I 'know' what looks right, and I won't allow for anything that doesn't look right. That doesn't solve all problems, but can certainly cut down on a large amount of them.

What I did see a lot of though in a lot of the case studies/readings/etc, was seemingly anytime advancements were made in one area, closing off particular patterns or styles of exploitation. The energy and resources often would switch to another domain, and there's a mad scramble to solve it.

Just my two-cents, and a bit off topic.

I’m a programmer and having taken graduate classes in Security Analytics and have a hard time convincing myself that I’m security savvy.

It’s such a cat and mouse game that has massive jumps in acceleration when it comes to ‘novel’ ways attackers create new exploits.

Having Apple taking it seriously even for people like me is a huge win.

We see it all the time with feature driven development. Users in general always want more.