weeksie

If you don't see the massive structural difference between the practice of pure mathematics and the practice of software, that means you misunderstand both software development and mathematics.

As I said above, that's with "WHOLE APARTMENT" checked. What I saw above was for a 3 day stay that for some reason defaulted to November. Those are 100% illegal and they are all available.

Here, let me do the legwork for you, this one shows 413 stays:

https://www.airbnb.com/s/New-York--New-York--United-States/h...

Ah man, sockets. Real sockets. Yesterday's kiosk thread jogged my memory about all that but almost all of the network communication on my old kiosk installations was socket based. It was a pleasant way to work.

If you just open Airbnb to nyc and check whole apartment there are like 800 listings right off the bat.

I had a kiosk software company for several years. Sold my part to my partners in 2008. We used Windows embedded for the hardware most of the time (until Mac Minis came out) and Flash for the front end.

I built out a Lua based server that lived on each of our units and communicated back to home base for updates using svnlib to grab changes. It was a pretty neat system, lots of hardware integrations and so on. Super fun. Lua was nice because its FFI is so pleasant to use. Flash was absolutely amazing for handling the UI. Our kiosks looked _so_ much better than all of the other hideous Motif-style UIs out there. Hell they looked better than most kiosks still look these days.

If you lived in Australia in the 00s and ever stepped foot in a Westfield or Stockland mall you'd have seen some of our kiosks.

Define exploitation.

The usefulness of metadata in rest responses ended up not mattering as much as people thought in most cases. Pagination is the best counter example but many rest apis do return next/prev links in the payload or in the headers. It’s still REST but the parts that mattered (http verbs for semantic info, etc) stayed around.

This is only true for native stock Americans. Immigrants do very well here, and it's far far easier to become rich in America than it is anywhere else. The American dream is as real as ever. Income mobility could be a bit easier in Australia, I guess, but I'd be hard pressed to think of many places where it was as possible to climb the social and income ladder. Of course, in America we don't have much of a safety net, so if you have ambitions to climb you gotta be careful not to fall.

Usually a lambda calculus interpreter is the first thing I futz around with.

I lived in Sydney for five years! Great city. Lived there before I came here.

My partner and I are looking at Madrid. But yeah, there is no other city in the world that's going to be like NY. Maybe London but of course that has the same problems.

My partner and I have been agonizing over this exact dilemma. We have an income number and an expenses number and when those cross a certain point, we've gotta go somewhere else. So there's a very good chance that we'll immigrate somewhere in a few years. But yeah, try as we might, we couldn't come up with another US city that either of us would want to live in.

Bright eyed PMs whispering "statistically significant" to themselves over and over as they nervously scan their data aggregation dashboards for wiggles.

I get it, you're _really_ invested in RTK but man, I just find it to be the right answer to the wrong question.

Since we last talked I have worked on projects where rtk was used because the devs didn't really grok redux and so far that's the best use case I've run across. That said, now when I run across situations like that I tend to guide clients to simpler state management solutions instead of piling on another layer of abstraction.

The problem with redux is that it's a simple, extremely powerful tool for creating a CQRS architecture on the front end but very few people treat it that way. Instead they bolt on things like rtk and add yet another layer of abstraction over their project. In those cases it's almost always better to just use something small and simple like Zustand, which the article called out.

For bigger projects, custom middleware is where the magic is. If you don't understand redux well enough to write your own middleware (it's not very complex, it's just under documented for some reason) then it's better to use one of the other, simpler abstractions instead of adding one abstraction (redux) then piling on more abstractions to make it usable.

Saga is so heavy and overly complex and you don't really get much out of it if you understand how middleware works. There's really no reason to add a huge dependency to your project.

You can do all of that pretty easily with a vanilla redux.

You don't need _any_ of that. You can use vanilla redux and put your asynchronous code in middleware.

Back in the 00s we put an easter egg into our mall kiosk wayfinding software. If you pulled up the software keyboard and typed in the name of the company it would show a card deck animation of our pictures. That was always fun to pull out. Used to have tons of them in the Westfield and Stockland malls across Oz. Wild to even think about how long ago that was.

You're wrong. If King Cove was growing at a good clip, you'd have a point but as it stands it's just a remote relatively static Alaskan town. I could point you at my own home town which is at the edge of the Prince William Sound and nearly unchanged over the last 50 years. A few new buildings have been built, and a few have gone down. They did build a new harbor in that time, but Cordova has not turned into Anchorage and it would be brain-piercingly stupid to believe that it would.

Atrocious to me that anybody would want to block that road. A mine? Sure. Logging? Yup. Oil exploration? Yeah. A gravel road to an airport in Alaska? Come on. I haven't lived in Rural Alaska in 20 years but I was born and raised in a fishing village. People in the lower 48 have no understanding of the vastness of Alaska and how small a concession this really is.

These specious environmental lawsuits are why no infrastructure has been built in this country in 40 years. We need to protect the wilds but a regulatory structure that allows vetos of a gravel road to the airport? What the hell.

This is really wild. It feels almost like a way to wedge dependent types into the system, at least that's what the MinLength<2> & MaxLength<5> stuff feels like. Amazing.

How was it digging into the compiler api for that stuff? Every time I've poked around with that it's felt like a mess. Any resources you'd recommend?

It's grey goo for human culture.

Attention is finite.

This is one of the reasons why I have pulled back from social media. In feeds I see a random sample of the most anxious people I grew up with and find myself knowing more about their lives than I do about people I care about. I'd prefer to spend my finite attention on relationships that are actually important to me.

The failure mode I usually see on experienced pairing teams is overly complex code. There's a certain flavor that I can usually pick out and be pretty sure that a couple of Pivots or Carbon5 or whatever pair shop has been working in a codebase. I wish I could be more specific about what sets me off, but I've called it blind enough times to think that there's a real effect.

Not that single coders don't produce weird code, just that I've not experienced a situation where pairing has been a win—with the BIG exception of doing code reviews.

I don't like it for myself because I don't work well that way. I don't like working at companies that use pair programming because most of the code I've seen come out of pairing sessions is not very good. I realize that's likely to start a religious war in certain areas but I've been doing this for 20 years and that's been my experience so far.

I think pairing sessions can be great for teaching or for getting some needed distance from a problem, but as a mode of production I haven't enjoyed my experiences with it.

I was happy to see he mentioned "pair" reviewing. I detest pair programming but pair reviewing is excellent. Whenever the time and culture of a place permits, I do everything I can to walk through my pull requests with one or two people. It's such a high value activity, especially when it comes to teams with a good mix of junior and senior people.

Sure! Informally, it's when there is a disagreement about methods of finding truth. In practice that's when the two positions in a discussion are using a different framework for deciding what's true in the world.

Are illnesses caused by bad humors or are they caused by an imbalance of cold and hot foods? That discussion will eventually reach a point where both participants realize they're arguing about theology, but it'll take a little while to get there. Once there, it's not like there's nothing left to do but unless both sides are willing to go "hey we disagree about truth here do you want to talk about the reasons why instead of the object level stuff about what's true" it's better for all involved to just smile and call it a day.

Avoids a lot of less filling/tastes great shouting matches

In that case I disagree strongly with your premise, but that's fine. I don't argue past epistemological closures but (sincerely) thanks for the discussion!

Ah, I guess I misunderstood. Would it be fair to characterize your point as: AI art isn't art but neither is most conceptual 20-21st century art so why does it matter, we're already living in a world without art?

If that's your position, I have some sympathy for that but I'd say that the difference is that in a world where AI art can be generated at the push of a button, we end up in a world where it's impossible to determine if a piece has been made by human hands. The cultural equivalent of grey goo.

To me there's a big qualitative difference between some art being bullshit and (effectively) 100% of it being bullshit. Of course that includes narrative art as well, since GPT-N language models are already pretty capable in that department and will only be getting better.

Read the article, he addresses this exact objection.