Hacker Newsnew | past | comments | ask | show | jobs | submit | saluki's commentslogin

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 used to use Soundtrackers a lot on Amiga in the 90s. I'm also pretty ok with using Reaper as a DAW playing all the instruments. I would have no idea how to get into remixing though. How would you suggest starting that? Do you tend to start with isolated tracks or just the whole mp3 and take sections and move around and add parts>


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.


I read "The Martian", found it an okay read and didn't bother to read this one. I'll reconsider.


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.


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.


Why is the siloing so important do you think? I think with all the use of LLMs now, entire functions or multiple functions can be done by 1 person. Those people can get a lot of task and skill variety in their work.


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.


My mental model of the 'new normal' is end users using AI to get their work done.

So if I re-worded the OP's description and replaced 'internal tools' with 'internal AIs' then this would at least seem like a more reasonable process to me...

> At our startup, engineers don't build features anymore. > They build APIs that internal AIs can connect to. > Most "features" like running an SQL query, sending a push notification when product X is ordered gets built by ops or product folks using those tools.

To me this describes a team of engineers that use AI-capable tools and that are building 'features' for themselves. In the way that us dinosaurs used to write build scripts.

I'm not saying that my mental model is right or wrong, just that working this way seems reasonable if you buy into my model.


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: