saluki

Having great success with Claude Code.

Short claude.md file, skills for various things like db schema, etc

For larger or complex features do a design session with claude, review design and make suggestions and collaborate, once design is dialed in ask to break in to tasks then do similar session collaboarating on plan.md files for each task/phase then have claude build it.

Claude is really really good at adding tests, leverage this for near 100% test coverage and it can also test that it's meeting the PRD/spec.

It's also creative and seems to like collaborating on the design and plan parts join in with that. Claude feels really similar to my favorite engineer I worked with as far as collaboration and even banter. It's nice.

Using claude code in the terminal btw, md files go in repo so all team, devs, consoles can see context across front and backend.

Use PRs run claude code review, I created a Minority Report style review skill as well, code quality, security, performance with anderton as the judge/orch

Then we have a human review PR as well

This process we are getting good code and faster velocity for sure, vs traditional SDLC for solo and with team

As far as reading the code, I think that will become less and less as long as it passes automated code review, it's performant, meets the spec and tests pass . . . SHIP IT

Watch DHH's recent RailsConf keynote, this is where we're heading, buckle up

No No No, start building websites with Claude Code, even if you don't know the basics of coding that's going to give you a better and more secure website.

WordPress was a good idea over a decade ago if you were doing affiliate marketing and couldn't code. But now everyone can code.

Brother Laser B&W

Soc-2 Type 2 is a lot of work for solo-ent. and you might have issues meeting some of the compliance with only one employee there won't be checks and balances. We worked with a local firm and their fee was around $15k but there is ongoing verification. Also there is a process you have to follow moving forward that's probably the largest cost.

I'm not sure SOC-2 is even valuable for most smaller apps. As it's compliance is more aligned for financial apps.

It might be more valuable for you to have a security audit instead of SOC-2.

I started DJ'ing last year I'd almost start there with a FLX4 just to get in to the music more.

I just started with Ableton recently working on remixing tracks I like. Actually working on a remix of Ella Langley's Be Her just because I thought it was a cool genre bending remix.

After you do some remixes creating your own from scratch will be easier.

Mimicing songs and artists you like is a good recommendation, you can also cut up and remix parts of songs you like.

I shared the one week trial links with my team and everyone is picking it up and getting productive. We share tips and tricks, best practices in a slack channel.

YES, now is the best time in history to build a software startup.

Copying isn't your biggest worry.

'French military victories'

Project Hail Mary, I laughed out loud and mocked the premise of the book but it was a great read, one of my best reads ever. Very well done.

Everyone has their typical 'work day' so you just get used to everyone's schedule and planned zooms around that and use slack for general communication. Occasionally I would msg or zoom outside of my core hours but we also had flex time so it worked out well. We generally always scheduled meetings through google calendar so timezones were handled there for coordination. If we mentioned a time in slack or on a zoom it was always given as NYC. It was a non-issue, motivation, sleep, food aren't related to this. Some team members worked later in the day in their local time zone by choose to overlap more with NYC.

They look and feel similar to the user, I still think native is better but React Native looks and feels pro so I'm cool with it.

I've been fully remote since 2012, you'll get the hang of it.

My teams have used a lot of slack msgs and slack huddles, lots of zoom meetings so everyone feels pretty connected.

It's great if you can meet up together at least once a year, work out of an office together and go out, grab drinks, eat meals together for team building.

You'll need a routine, exercise, taking breaks, leverage flexible hours, take a trip and work remote from somewhere cool and interesting.

Take breaks to cook a meal, laundry, play guitar for 10 minutes, get outside for a quick walk, enjoy your pets, say hi to your family, have lunch with a friend, you won't go stir crazy.

Being remote is one of my favorite things about my career, I love it.

Every team member has a job to do in the software process. Each speciality can leverage AI to perform faster and better moving the whole process forward. I think everyone can expand outward with what they are able to do enhanced by AI but they need to stay around their core expertise where they are bringing the most value. Things still need to be maintainable and secure.

Definitely ...

If anything engineers are doing more with AI and aren't limited to just APIs.

They are building more of the UI/UX, Design, Front/Back + API instead of less and meeting/building product's vision.

Supported by Devops.

Every layer of the process will be enhanced by AI so everyone is doing more that our previous process.

I wouldn't limit any layer, enable everyone and every team to do more and be more productive.

This is not the new normal.

Engineering should be doing the engineering.

Product should be doing product.

DevOps should be providing infra.

If end users want to use a report generator or setup a notification rule that's one thing but duct taping features together never is sustainable.