#558: Hyper-Personal Software with Python

Let's take it out a bit and talk about sort of internal company software.

There's a, a lot of people listen to this show who are not what you would call enterprise developers, right?

Yep.

They are students, they're maybe data scientists kind of on, on their own, or they work at a research, or they work at a startup.

So give us a sense of what internal software at, like, these bigger companies looks like today and, like, maybe fi- you know, before the AI world and, and so on.

Every company is different, and I'm sure you've experienced that as well.

Lots of, uh, different operating models.

But I guess enterprises always need to make sure that things are orderly to some degree.

So when I work on my MacBook as a solo practitioner, I can make decisions about, uh, what software I wanna use, how I wanna use it.

Ideally, when I'm working with data, you've gotta make sure that you've got certain controls in place.

But within companies, those things really matter, right? So you do need to make sure that things are, uh, secured appropriately, that people only have access to the things that you want them to.

So I think in that context, there's always gonna be sort of overheads and friction on developing any sort of software.

So you've just gotta be aware that you need to allow for those things.

So I think the idea that we'll talk about coming up is, uh, the sense that, uh, when you're actually working within a team, within an enterprise, maybe there's certain things that you can do that don't need to impact too many other people, and therefore, you can achieve a greater, uh, degree of autonomy.

They're certainly the things that you need to be thinking about within the enterprise.

So it's not choose your own adventure.

It's a work within the, the constraints which are appropriately there.

And particularly, uh, between industries, you can have some industries which have little regulation, and then in other industries they're, um, highly regulated, uh, for very good reasons.

But again, that can provide a, an additional layer of complexity as you start to think about how, how you develop and what you develop.

I've not spent a ton of time working at large companies.

I worked at a company for maybe six months that had 1,200 people, and I got there by being acquired from a company that had 10 full-time employees, so it was a little bit of a shift.

But I did do professional software training for a long time.

So I taught week-long courses at over 100 different companies and, you know, you just... [laughs] You get a look inside these places, you're like, "Wow, this is...

This one is really different," and, "This is, like, really, uh, unique in this way or that." But the...

one of the...