The thinking mode is super-useful to me as I _often_ saw the model "think" differently from the response. Stuff like "I can see that I need to look for x, y, z to full understand the problem" and then proceeds to just not do that.

This is helpful as I can interrupt the process and guide it to actually do this. With the thinking-output hidden, I have lost this avenue for intervention.

I also want to see what files it reads, but not necessarily the output - I know most of the files that'll be relevant, I just want to see it's not totally off base.

Tl;dr: I would _love_ to have verbose mode be split into two modes: Just thinking and Thinking+Full agent/file output.

---

I'm happy to work in verbose mode. I get many people are probably fine with the standard minimal mode. But at least in my code base, on my projects, I still need to perform a decent amount of handholding through guidance, the model is not working for me the way you describe it working for you.

All I need is a few tools to help me intervene earlier to make claude-code work _much_ better for me. Right now I feel I'm fighting the system frequently.

If this device delivers on audio quality it's totally worth it at $59.

When I built blanket forts as a child it was something new, my first attempt at building something. It was exiting to figure out how to do it, and enjoy the end product. After a few of those it became a bit more usual, and I started doing other things - play with model cars, build lego sets, etc.

I recently tried welding and I felt that same tinge of excitement - I'm gluing metal together! It's basically magic, I'm taking separate parts and turning them into one. I'm not welding purposefully or to build something, I just really like the act of welding.

Welding was new to me, I never experienced it. I think as a child I everything was new to me, the way welding is. I approached the world with a curiosity that drove me to play with it, to figure it out.

But now I've figured a lot of it out. It's not as fun to play with anymore, because I've exhausted all the angles of play I could come up with (and I did that a long time ago).

I still find that curiosity that drives me to play with something, to figure it out - but I have to look for it, find aspects of life I haven't experienced yet.

Ctrl+F on the page for "System prompt" doesn't show any hits. Given how important those are for ChatGPT (another thought - was the author testing GPT3.5 or 4?) I'm not sure how much weight to put into the ChatGPT results either.

Not sure how much I can take away from this comparison.

Our challenges with multiple repos mostly revolved around builds and orchestration. We had to apply all build/deploy changes to all repos, and that increased the chance of doing some small thing wrong. Finding what exactly is wrong with one repo that should be the same as all the others was like one of those "find the differences" pictures. Really annoying.

This is more microservices than multi repo related, but making sure all the different services are released in sync was hard and annoying and often caused issues. Eg a specific API was updated and released but the for a consumer had to be rolled back and the rolled back version wasn't compatible with the new API. So current version and roll back wasnt an option. Rolling back the API would require rolling back all consumers but crap, one of the consumers applied a big migration to our core database and rolling that bank would take forever. And so on.

Just tons of little edge cases that went wrong at the worst time because it was so hard to foresee all the issues.

Monorepo and monolith is so comfy. Want to share code? Move it up one or two directories and import from there. No issues with two bundled react versions in two builds. Easy to refer to code from other teams, never an issue that someone forgot to add you to that one repo almost no one uses but that you need to commit to during firefighting.

I'm not saying multi repos/micro services can't work, but it's hard - you need strong processes that prevent people from being lazy, you need monitoring and management well defined, you need extra tooling that's aware of the repo structure, you need a strong story around migrations, and so much more.

I currently work with a mono repo monolith that over a thousand devs contribute to daily and it's Cindy comfy. It feels much easier to fix too many devs in one repo (primarily via strong compartmentalization) than to fix too many repos/services

There seem to be a lot of people thinking front-end is just a mess of different options all doing the same thing. And the same people show little understanding of the complexities and nuances of front-end solutions.

I'm happy to answer any questions you have, salary too, if you send me an email. Sadly I can't publicly disclose our salary range, so if you're willing to bear with me and jump through the emailing-hoop I'd appreciate it.

- Thomas

Lasso is a leading CRM for new home builders and real estate developers. We've been modernizing our app for the last few years, moving from a PHP stack to an Angular.js app and a Java-based REST API.

Now that we're done with most of the legacy-porting work, we've got a lot of new features to build and that's where you would come in.

As a Senior Front-End Developer you would take requirements from the Product Lead, create wire-frames and mock-ups, gather feedback via user interviews and finally implement the features in ES6, RxJS, Bootstrap and Angular.

We offer:

- full-time remote work. Most of our developers are working remotely all over Canada. However, if you prefer working in the office you're welcome to go there. It's located in Richmond, BC.

- when you start, we'll provide you with any hardware of your choosing

- a tools budget of up to $300 per transaction you can use to buy whatever you need to stay productive - no authorization needed

- formal education matching (up to $1500 yearly) and funding for other continued-learning courses, conferences, and workshops

- competitive Vancouver salary

Lasso has a very trusting and open work-environment, without fixed work-hours, imposed dead-lines, or in-office requirements. That does require you to have good time management skills, and be comfortable with self-directed work.

If you're interested or want to know more details, please message me at thomas@lassocrm.com (include your resume if you're applying :) ). I'm the front-end lead and have been happily working here for four years.

I moved back to my parents for about a year to work on other side projects, but ended up looking for a job and found an awesome small company that I'm very happy working for. I'm still working on market-focused side projects and without the stress of having to make money/gain traction it's a lot more fun. I really prefer this setup, especially since a small company allows me to scratch most product-development itches I have since there's not a lot of bureaucracy.

A lesson I've learned: Quit early. If you feel bad about the project right now, end it as soon as possible As in, tomrrow. Don't stick around waiting for the big break. I've done exactly that, and while we actually ended up with some paying customers after our pivot, we would've had to achieve an insane growth to be worth anything to my co-founder and me due to the dilution of our shares. It's not worth basically building a new company for the smaller fraction of shares you have after taking an investment.

If you are developer, please use it on your next prototype instead of throwing together some html and css.

She's not saying "this is going to be a professional design for your next project", the title itself contains "half-decent".

She's providing insightful tips for developers to make their pet projects look..like they're not designed by engineers (we do tend to make a mess of things).

And the advice she gives is perfectly fine for exactly that. There are fonts that look good together, subtly textured backgrounds do look better than simple, flat colored one's and using basic color theory upgrades a websites look (teal vs. orange, cough). Together, they make something that looks half-decent.

Just like the author claimed.

http://www.splashdata.com/press/PR121023.htm

There's no reason why you would have a three attempts limit, or five, or ten, and so on. If I get three per account, I'll just use the top three and try again different accounts. If I get three attempts per IP, I'll use many different IPs and do the same.

To remain user friendly, delays are the way to go. E.g. you could have three different delays that add to each other: Account-level, IP-level and global. Increase each with every failed attempt up to 30 seconds of wait time, and add them together. This will slow down brute force attempts to the point where they're useless, while still allowing legitimate users to login (just with a little inconvenience).

As a result, if I failed three attempts with one account, and three one next, etc., my IP-level limit will prohibit me from moving on to other accounts. If I try a lot of passwords on one account, the account-level and IP-level ones will slow me down. And if there's a distributed attack with many IPs, the global delay will reduce the damage the attack can do. All the while legitimate users can still use the service.

"how to start an airline" came up a couple of times in this discussion. If you ask an existing airline "How should I begin?", they might see you as a future competitor or as a waste of time - either way, they won't gain anything by helping you.

But plane manufactures do gain something from helping you. Even if only every millionth guy looking for advice actually buys a plane, it's still worth it for them. In face, you can check out Boings guide on how to start an airline:

http://www.boeing.com/commercial/startup/

I'd wager that it's the same in other industries. If you want to start a cable company, talk to the people that'd profit off of it - people selling routers, contractors that build the infrastructure, helpline operators, etc.

Starting a wiki is a great idea, and there's already some information you could copy/link to (depending on the license). You'd have some information right off the start.

You could abstract away all the web and phone (press '9') stuff and just have a button "Open the door? Yes/No" if someone activates the buzzer.

Maybe add some easy management for pins that:

- always open (roommates/family/friends)

- open only one time (deliveries, not-so-close-friends)

- open only under certain conditions (time of day, day of month, etc)

Make it possible to easily share those pin numbers via SMS, Facebook, email, etc.

I think you have a product that's great for access management. You should highlight the additional benefits in your marketing, e.g.:

- easy to invite friends over for dinner

- easy to share apartment without the need for new keys

- easy to revoke access

- easy to let cleaning staff in during certain times of day

Another thought: Market it as a helpful add-on for AirBnB customers. You don't have to give someone a key to your apartment, just a PIN that only works for the time they rent the apartment (this is also useful for sub-leases). You can revoke access at any time, no matter where you are (big problem with keys).

Short version: I think you'd have a better chance packaging your product as a mobile app, abstracting away all the web/phone stuff and sell it as "entry management" instead of "automated buzzer".

I'd interpret the "Basically" section as a display of their intent, since the full terms require a lot of legalese to protect 500px.

As NyxWulf and other commentators said, the "Basically" sections would probably play a role in a law suit anyway, so they couldn't hide contradicting terms in the left section.

Could you please outline how google.com is turning into a web portal like yahoo.com?