verelo

I wouldnt say it is, but there are circumstances when speed is helpful. I wouldn't argue that coding is one of them.

This is the feeling i get too. Cant produce quality, but can produce something that is super fast...so take the wins where they are.

pretty nice, the click targets are a bit awkward but otherwise really fun!

Maybe in the US, in Canada i find their online services are pretty average. A lot of the time i search for something and i get a US link, much to my disapointment.

Yeah, home depot is a tricky case. They have a huge array of products, and in my experience when you cant find something you need to search beyond the store you're in....so the database you need access to isn't exactly small. Makes a practical offline experience tricky.

Home depots website sucks anyway, slow, clunky, terrible touch space, and the search is awful.

Aside, they should ad cell repeaters inside to fix all this.

I used to run a company (2010-2018) where our customers were almost always using our product inside of grocery stores, which are almost always metal sheds with some finishings on the walls. Not so great for cell service, it became essential for us to support offline mode if we wanted to keep those customers happy and engaged.

I spent many late nights trying to debug reachability bugs. It's frankly a nightmare trying to build a reliable app when the user has /some/ cell service, but not enough to operate the app reliably.

So i've done similar things in the past - and my justification for 'app' over website has been offline.

Does the PWA state of things resolve that in the modern days? If it did, yeah I'd agree, no need for an app at all. In my case the app was being used in rural Ontario. I cant even make a phone call here without wifi.

That checks out.

As an Australian, Apples voice models have always sucked. I've tried using stt (again) more recently and its improved, but i'm so tired of having to Americanize my voice to get it to figure out what the hell i'm saying.

That success rate aligns with mine. I was also shocked, at first.

For sure. I mean, i think naturally you'll end up there if all goes well. Have some tricky questions prepared of course, but starting simple gives you so much so quickly and often tells you where their strengths and weaknesses will end up being.

I'm not sure if its best to focus on strengths of weaknesses, but i did prefer to focus on strengths. I found convincing myself why I do want to work with someone was a better experience than trying to find reasons not to. Also it just tended to get better buy in from the other team member that way, and i'd know how to assign work once they joined.

ha, i'd have loved that. I'm out of the world where I hire people these days, solo founder life. Maybe i'll go back there, but it's a real mission objective to just be a one man show right now.

So for about 10 years my main interview question was:

"Write me a function in any language of your choosing, that takes an array of integers and returns the sum."

I loved it. Here is why:

1. I'd get to see them write code, in a low pressure way, but they'd have to write something

2. A shocking number of people would struggle to write the code. That was my signal to end the interview early.

3. I'd get to ask "So tell me how it works" and they'd sometimes look at me like I'm a moron, but others would be respectful and kind, and that would tell me how they'd answer other people who ask questions they felt had obvious answers.

4. I'd ask "what could go wrong at runtime?" - this would be where most people got surprised by their own responses, but it was a fun conversation to have about a seemingly simple function.

5. I'd ask how they would fix any potential runtime exceptions or potential undesirable behaviours

6. I'd try break it, and ask how they would handle that (if i could, i often could)

7. If we got this far, then we could move onto other questions and they're warmed up and generally feeling safe about how the conversation would go. I'd like to switch from coding into data structure related questions normally.

I hate high pressure coding interviews, also, who the hell doesn't just sit there and Google / LLM the answer anyway. The real question I want to know is "How curious are you? Do you want to learn? What kind of person are you? Will I enjoy working with you when things get hard". That's hard to figure out, but you're not going to do that if you just try stump someone in an interview. I think it's on the interviewer to find a way to ask questions that are revealing and accessible in an interview environment...and frankly, I think you get more out of it if you make the effort to keep it simple.

That's what Google told me, but i still don't see how it links to this?

I'm glad you're asking because I've seen it too and don't get it either. I assumed initially it was alpha as a typo, then I Googled it and got even more confused.

Land of the free, clearly.

None of those things are knowledge. I think theres something specific around limiting access to knowledge and capabilities that makes this feel insidious.

Some do. Sr-22 for example.

However, often if you’re handling things well, loosing an engine isn’t the end of the world.

A lot of accidents happen very close to the ground, at height wear a parachute wouldn’t necessarily be helpful anyway.

A parachute, a great solution for some scenarios, but for many, it’s not going to change the outcome. Such examples would be mid collisions, low altitude spiral dives, fires, or anything related to a shortage of oxygen. You also need to consider that during a lot of accidents, other factors, such as weather might be impacting the decision matrix of the pilot, and that might prevent them from using a parachute until it’s too late.

The parachutes are also another maintenance item in increasing the cost of running the plane, and generally, the airframe won’t survive the accident, so people are hesitant to deploy them.

Given the trajectory of the world’s on, it seems pretty obvious to me that diversifying from oil and gas is required for a long-term sustainable economy. I think the more interested in short term benefits than long-term success.

The irony that they figured out how to eliminate rats, but can’t diversify from oil and gas is pretty special.

So, I love this little game. I've been wanting to remake Scorched Earth for years, just for fun.

Decided to experiment with this repo today, adding multi player, islands that can sink the ships (that the ships cant shoot through), and a few other things to the game. Anyone who wants to join, ill be in here in a multi player room that supports up to 10 people at a time: https://ndroo.github.io/pirates/?join=BP4Q

I also added controls for mobile users, because that was the first issue I ran into. Probably buggy, maybe not secure...but i had some fun with a friend a few moments ago and it wasn't awful.

Thanks for sharing this OP!

Probably a bit but here’s the thing: if charging fast is, well….faster…then people care less if they loose a little extra battery because getting it back is less inconvenient.

There’s a graph i imagine here where slow charging, you want to retain all capacity. Faster it gets, you tolerate more battery loss.

Yep exactly this. The app developers are the problem, but Apple and Google are not helping here.

Came here to say the same. I don't even know what this product is anymore. The website makes it sound like its about music but there is no music? I'm lost.

The last time I paid for LastFM was some time in 2009...but the home page just isn't clearly telling me what the service offers.

Yeah, all my chargebacks are Americans. Realtors are the worst.

A good Tl;dr; is never a bad thing in a world where everyone is being pulled in different directions for attention. I agree with you for the most part, but after reading the post, it's a mess and could do with a clear summary at the top...hell, even an index of relevant sections and sub-headings.

So unfortunately this is it for me too. I liked Cursor as a tool, but when i switched to Claude I realized i was getting WAY better value for money. I spent $1800 the month before, i spent $200 the next.

I'm now switching between Claude and Codex for less than 1/4 of what I was spending in December.

You folks are amazing, thanks for catching that. My curiosity is soothed!

Great initiative.

However I am curious about the "NO USE FRANCE" text at the end of this article. Is this a licence issue or something? Would love it if someone with insight would be able to comment!

Like any scale system, degrade the experience. Use radio if the more advanced systems are unavailable?