DEV Community: Stephen Sauceda

A.I. As I See It

Stephen Sauceda — Sat, 09 Nov 2024 17:00:47 +0000

Do you remember when you were just starting out as a developer? Remember that feeling you had when you FINALLY got some code to do The Thing ™️ you wanted it to do? That "drunk with power" moment that had you believing you could build anything? That feeling that made you think "this is what I want to do for a living"?

That's the exact same feeling A.I. is giving to a lot of non-coders right now.

But There is a Difference

When we had that feeling, it's (likely) because we finally understood the code that we wrote. It's a necessity, most of the time, in order to get code working.

"My code doesn't work and I don't know why - my code does work and I don't know why" jokes aside.

When a non-coder gets ChatGPT or whatever to spit out some code, I would venture to say that, most of the time, they don't understand it. It was just handed to them with (presumably) a set of instructions on how to run it. They got the baby without the labor. In my experience, a lot of the time they even require a dev to run it for them (if they're trying to integrate it into existing code), fix it if it doesn't actually work, deploy it and all of that.

But, when it does result in something that "works". It's still that same feeling.

What It Could Mean

In my opinion, it means that, just like is wont to happen with new "real" developers, the Dunning–Kruger effect comes into play. And I swear, I don't mean that as a slight at all, to anyone. It's simply a common consequence a lot of us go through as we learn new things, myself included.

So that sense of empowerment, combined with (perhaps) an overestimation of confidence, also combined with the notorious hype cycles that tech goes through, can lead to some bad opinions and decisions.

A.I. is the new "pivot to video".
- me on Threads

More and more "simple" code could start being produced by the non-coders of an organization as a means to not "bother" an actual on-staff developer. Before long, the question could start being asked "do we need this many developers if A.I. can do so much of it for us?"

How We Earn Our Keep

Because we, as developers, understand code, we should be able to build some wild shit with A.I. We should be able to write code that helps train and tune models to do things casual users (and probably even "power users") of A.I. simply can't.

Everyone wants a chatbot, apparently. This, in my opinion, is the most boring and generic use of the technology. But they can be quick to spin up and seen as a somewhat easy win. They are also (again, imo) a consequence of a lack of understanding of the technology, a lack of imagination, or some combination of the two. And, as I've said before:

Engineers have a unique perspective on products because we actually build them. We know the technical limitations. We know the caveats. We know what's actually possible.

The way I see developers protecting themselves from A.I. "taking their job" or whatever, is to understand the technology and show people the kind of stuff it could/"should" be used for. Simple development tasks are quickly becoming table stakes for A.I. so the way we show our value is by doing the "Holy shit!"-style stuff with it.

The Caveat

The problem with more deeply understanding the technology is knowing that, in it's current (and maybe forever) state, it is inherently an unethical technology. Bias, accountability, copyright, environmental issues. The list goes on and on.

And a seeming theme in tech is to ignore these issues. Whether it's ignorance (willful or not), an expectation that "it's not my problem to solve", or a ride on yet-another hype train in tech, people are rushing to include (and advocate for) A.I. solutions and features in pretty much every product they produce lately, mostly in search of a buck.

I Don't Know What to Do

It's a number of different catch-22s for developers. We're "fighting" with people experiencing the same feeling of empowerment that got us into this industry to begin with. For self-preservation, we have to understand and demonstrate how the technology can be used "in the right hands". But, for a socially and morally conscious developer, are there really any "right hands"?

It's an interesting time. "Interesting" isn't the right word, but it's the first word that comes to mind.

Remote Control

Stephen Sauceda — Wed, 03 Jul 2019 03:32:04 +0000

Photo by Wilco Van Meppelen on Unsplash

Next month will mark my fifth year of working remotely. Like a lot of people who have worked remotely, I don't know how I would ever be able to go back to working in an office. It just feels "right". Of course, I could potentially be one of the more introverted people on the planet so working from the comfort of my own house might just suit my personality. Anyway, after five years, I have some thoughts on remote working and how I've managed to do it successfully (I'm still employed after all) so here we go.

Photo by Piotr Wilk on Unsplash

Set Up Your Space

This is the single most important thing I think I did for myself. From my first day of remote work to today, I've had "my space". Initially, that was nothing more than a desk in the corner of my bedroom but it was mine. It's where I go to do my work. When I sit there, I am working. I am "on". Some people may be able to work effectively on their couch or bed but not me. I need a space. And I need it set up the way I want.

I am quite particular about my space (now a separate office in our home). I am constantly trying to find that thing that doesn't necessarily make me more productive but makes me more comfortable in my office. I feel like if you're going to spend a lot of time in a particular place, even a specific spot in your home, you should be comfortable. So I've spent a lot of time obsessing about what that means for me. From the posters on the wall to the color temperature of the light bulbs to the peripherals to which I dock my laptop, I've gotten rid of anything that didn't spark joy and replaced it with something that does (or not replaced it at all).

I've worked in a number of offices for a number of companies and I just don't feel like the workspaces I've been provided (even my own office on location) felt like "my space". It felt like I was borrowing it, because I was. Even within my own home, having MY workspace has greatly enhanced my comfort while working which, I think, has improved my productivity as well. And keep in mind, my happy place is my home office but yours may be a coffee shop or a library or somewhere else. Just make it somewhere you're comfortable.

Communication

Since we started off selfish talking about something good for ourselves, let's talk about the single most important thing you can do for your team: communicate. As much as you can. Really. One thing that can slip your mind when you're in your home alone, staring into a computer screen day in and day out, is that you're (most likely) operating as part of a team. Teams communicate. They accomplish shared goals. So don't let yourself operate in a vacuum. Let people know when you're in and when you're out, what you're working on and where it stands. Talk about challenges as soon as you're aware of them. Be honest about progress (or lack thereof). If your teammates feel like they have to pry information out of you, that is not going to fly.

Secondly, remember that not all communication has to be serious. There are #random Slack channels for a reason. When you work in an office, you of course develop friendships. Working remotely, you have to try a little harder to be social. You aren't going to run into one of your co-workers on the way to the vending machine, right? Although if you had a vending machine in your home office that would be pretty badass. I digress... Talk to your co-workers. About work and about things that aren't work.

Don't Take Advantage

Remote work usually includes some level of flexibility not just in the location from which you work but also in the hours you work. It is easy to take advantage. I would venture to say that a lot of places will cut you some slack on a long lunch here or there or a day when you have some work being done around the house, etc. But if that stuff becomes the norm rather than the exception, expect people to notice. And I bet when they notice, it doesn't lead to good conversations. Most decent human beings probably won't ever even think about stuff like this but, just in case, don't be an asshole and you should be fine.

So that's really it. I don't think there's a ton to remote work, just a couple of fundamental things to keep in mind. Does it require some self-discipline? Yes. But I'm not the most self-disciplined person alive (I swear I'm just going to have one more cookie) and I manage to work remotely every day.