Message originally sent by slack user U7213XMGS3H
interesting
Message originally sent by slack user U7213XMGS3H
we’re trying to get some to L4 right off the bat but i wonder if we’ve got it backwards
yeah. Except for a couple super simple packs we have were defining a public API was super easy and then we put enforce_privacy: strict there.
I think there’s no getting it “backwards”… every project is different.
Message originally sent by slack user U7213XMGS3H
i guess i just mean we didn’t really consider what you’re doing
You should by all means do all the low hanging fruit first. If you can push something to Level 3 or 4 with a day of work or so… you should totally do that.
Message originally sent by slack user U7213XMGS3H
OK updated and maybe last version of our levels (now we’re calling them isolation levels). Thanks for some great feedback @oboxodo, <@U70TIGAX94P> and everyone else
I feel like pushing for Level 4 (and 3 to some extent), can be like pushing for 100% test coverage. Your ROI after ~90% goes down drastically.
I don’t know how a big app with all its packs in Level 2 looks. I haven’t got there. Once I get there, my opinion can certainly change 
but it feels way more achievable than Level 3 and 4
Message originally sent by slack user U7213XMGS3H
if you don’t mind me asking, how many engineers work on your app
Message originally sent by slack user U7213XMGS3H
(aprox)
currently 8. small team.
you?
Message originally sent by slack user U7213XMGS3H
~150
heh
Message originally sent by slack user U7213XMGS3H
i think we see these public APIs as a huge asset for helping our teams not trip over each other
Message originally sent by slack user U7213XMGS3H
it’s also very hard to get there
totally.
Message originally sent by slack user U7213U6VS93
I think we’re also intentionally being a bit aggressive with our goal setting too