Keith Whyte retooteado
Aral Balkan

If you don’t have the resources to write and understand the code yourself, you don’t have the resources to maintain it either.

Any monkey with a keyboard can write code. Writing code has never been hard. People were churning out crappy code en masse way before generative AI and LLMs. I know because I’ve seen it, I’ve had to work with it, and I no doubt wrote (and continue to write) my share of it.

What’s never been easy, and what remains difficult, is figuring out the right problem to solve, solving it elegantly, and doing so in a way that’s maintainable and sustainable given your means.

Code is not an artefact, code is a machine. Code is either a living thing or it is dead and decaying. You don’t just write code and you’re done. It’s a perpetual first draft that you constantly iterate on, and, depending on what it does and how much of that has to do with meeting the evolving needs of the people it serves, it may never be done. With occasional exceptions (perhaps? maybe?) for well-defined and narrowly-scoped tools, done code is dead code.

So much of what we call “writing” code is actually changing, iterating on, investigating issues with, fixing, and improving code. And to do that you must not only understand the problem you’re solving but also how you’re solving it (or how you thought you were solving it) through the code you’ve already written and the code you still have to write.

So it should come as no surprise that one of the hardest things in development is understanding someone else’s code, let alone fixing it when something doesn’t work as it should. Because it’s not about knowing this programming language or that (learning a programming language is the easiest part of coding), or this framework or that, or even knowing this design pattern or that (although all of these are important prerequisites for comprehension) but understanding what was going on in someone else’s head when they wrote the code the way they wrote it to solve a particular problem.

It frankly boggles my mind that some people are advocating for automating the easy part (writing code) by exponentially scaling the difficult part (understanding how exactly someone else – in this case, a junior dev who knows all the hows of things but none of the whys – decided to solve the problem). It is, to borrow a technical term, ass-backwards.

They might as well call vibe coding duct-tape-driven development or technical debt as a service.

🤷‍♂️

#AI #LLMs #vibeCoding #softwareDevelopment #design #craft

0
Keith Whyte retooteado
Lori Emerson

a 1990s-era Earthlink explainer that reminds us of a time when we still had the power (and the ability) to accept - or refuse #othernetworks (pic taken by @rose_alibi)

0
Keith Whyte

Looking for ideas; What to do with ? I have a few, and while they work well as voice call "telephones" on 2G and 3G networks, and they have a respectable camera, otherwise they are mostly useless junk. But there must be some millions of these things out there.

I understand that the more modern devices, latest releases even are now being reduced to useless junk in some countries.

I've up to now not investigated much about so-called , partly because there did not seem to be any easy access to applications to install on the thing anyway.

I used to be able to get some limited access to the app distribution operation run by Inc. but that now requires handing over personal data, and only for the tiny amount of apps still available for older

Of course, I would NEVER purchase one of these things and would never recommend to anyone to do so. Those I have were donations, although I did replace some batteries. I am not so happy with the idea of recycling perfectly funcional electronic devices. Recycling electronics (as in recovering the rare earth stuff) should really be a very last resort.

I suppose at some point, I might find time and inclination to investigate possibilities for actually owning these devices. But the question remains then still, what would you do with it?

* Did anybody ever create an archive of for ?
* What are the issues, with compiling and running apps from source?
* Is it even worth looking at?

0
Keith Whyte

@eris2cats
How about -
I wouldn't touch your shi**y centralised, spying, propaganda pushing "social media" Internet with a barge pole anyway.
That should be age verification enough
And if not, well, i use .

1
Keith Whyte retooteado
islieb?
1+
Keith Whyte retooteado
Torsten Grote

Google has news on what you will need to do for still being able to sideload apps:

* enable developer options
* confirm that you are not tricked
* restart phone and re-authenticate
* wait one day
* confirm with biometrics that you know what you are doing
* decide if you only want unrestricted installs for 1 week or forever
* confirm that you accept the risks
* enjoy the few apps that still have developers motivated to develop for a user-base willing to put up with this

goo.gle/advance-flow

1
Keith Whyte retooteado
heyokyay
1+
Keith Whyte

🙄 So, I just searched "remove snap data snapshots of removed snaps"

There are days I really wonder why is still in my life.

0
Mostrar más antiguos
Telecomunicaciones Indígenas Comunitarias

Servidor experimental para I+D en Intranets.

Recursos

Desarrolladores

¿Qué es Mastodon?

tic-ac.org

Mas…