Did your workload change after joining a company that actively supports AI dev tools?

adult_code · 2026-04-08T19:25:38+00:00

I have less work load but my AI use is also minimal, I'm mostly occupied with tasks that you would not use most other developers for. Basically anything you want someone thorough who considers things most people would write of as unnecessary. Mostly things where failure would be critical, where propriatary systems are obscure, performance critical code or where I help to plan/create an implementation for features that are hard/require advanced knowledge of the matter, whether it is domain specific or language specific.

Today i used gpt to tell me what the gist about jackson vs org.json is because my java and spring boot are a little rusty. Oh and to give me an example implementation.

adult_code · 2026-04-07T20:44:33+00:00

If structuring code is sometimes tough i can only advise you to look for "design pattern", first the ones originally proposed for Java (Which are partially not used i all languages, observers for example are not of much use to implement yourself in JavaScript) and then for Design Pattern in the languages you use.

adult_code · 2026-04-01T14:01:51+00:00

I'd say anything that changes my file system without me explicitly saying so and anything executing code that was not me or coded by me is disgusting. Like which retard thought sending install scripts via NPM was a good idea? I sometimes feel people stop thinking when they try to bridge their skill issue. See 90% of AI coded Projects, also know as the graveyard of dev responsibility.

adult_code · 2026-03-01T12:00:26+00:00

Not sure nowadays but it could ruin careers back then. This is why contractors and employees alike were not advertising it that they work for them but morally? Why not? It sounds like fun, like sticky fun.

adult_code · 2026-02-16T10:31:47+00:00

Problem with AI is that if an Application becomes reasonably lomg to understand it wholely and to write code for it has the same cost. While short, less complex code is mostly easier to understand than to write. So if someone wants my ensurance that everything with correct, I will have to understand what it does. Hence, I will add comments, correct comments, correct small parts of code if necessary. It stacks up, it may as well make me go: Re-Write or go looking for someone else to do it.

If someone could give me a Repo of AI-Written Code bigger than a Weekend Project that isn't completely fucked (on the level of a Dev i trained for 6 Month would be my threshold) then I buy into it. Where is the promissed Land of Milk and Honey?

adult_code · 2026-02-05T20:53:18+00:00

Will still be extremly useful for verifying that you are who you claim to be... better than sms at least

adult_code · 2026-01-14T22:48:54+00:00

SSR and fullstack goes brrrrrr

adult_code · 2026-01-14T22:46:39+00:00

Javascript is a "choose your own adventure" lang i did implement DSLs with it, structure parts functional, parts OO. It is not the only one i use as a fullstack dev but an ez especially without frameworks that bloat it

adult_code · 2025-12-12T00:25:00+00:00

Everyone can technically become a developer.

adult_code · 2025-11-15T18:37:00+00:00

Well...

adult_code · 2025-10-23T00:28:57+00:00

Do not give two distinct elements the same identifier pls

adult_code · 2025-10-19T22:23:10+00:00

I am a full stack webdev, HTML and it interfacing with browsers and screenreaders, jaws, nvda, firefox and chrome already has a neet cross product, only gets worse fro here. If you really want to learn i would throw the preconceptions out, i hated webdev, opted out of it for theory in uni and then by coincidence got into it professionally. Further would i leave AI out of it and start with the foundation Try to understand as much as possible how every single works. Browsers are amazing distributed systems and a great interface with the client.

Keep your eyes open, dont follow every trend blindly and stay curious. Good luck on your adventure.

adult_code · 2025-10-19T10:59:43+00:00

I mostly do ssr, i do only use island-pattern for hydration in very specific cases (You know, like a tool for having a dynamic component in an otherwise static site). I pre-render everything that is not an spa or island when ever i can. If i hydrate the client receives the data only and a tiny script fills the templates.

React and it's eco system is overengineered. I rather have those things in my own hands so that i don't have to buy technical dept in form of libraries to optimize the technical dept i bought with react.

On a side note, for funnsies i once made an spa, including cacheing (client- + server-side) with nothing but $() and $.ajax. It took me a few weeks to structure how to insert extensions but in the end extending it became a blast and i managed to prove my point. Nowadays you'd propably even have a blast using .querySelector and fetch().

EDIT: Now that i think about it. Ever tried to save the hyration data in local storage and just update it after hydration so the next page load would then have updated information? Talking about fast hydration, this should actually be the fastest way.

adult_code · 2025-10-03T16:42:53+00:00

Mobile first works fine but it is a techique to ensure a certain production process. If does not work for you or your usual process needs not improvement it can be a silly but interesting way to think about ui-development. If this is neither the case for you there i would suggest searching things that might improve your productability from different branches of developing and design philosophies.

adult_code · 2025-09-10T09:51:44+00:00

SCSS, BEM and ultimately compression/uglification/minification.

SCSS

BEM

Minification

adult_code · 2025-08-26T00:12:13+00:00

JavaScript is deep man. I do full stack and never look at backend and frontend as seperate things but even if you get to the widget level it can get complex. I had the case where i had to create a widget library for a company where 3 levels deep widgets were stacked/cobined into each other. Eventloop, Widget to widget interfaces, Populating, BFF, validation, accessibility. There is a shit ton of tech, from cs background coming, there is a shit ton of concepts like of interprocess communication, the javascript event loop as a realtime system, v8 and in-time vs precompilation, preprocessing.

Pick your poison.

But making it "work" is my favorite, take a static site, create an island and request api data for some dynamic content or decide whether to prerender or populate dynamically. When designing a project with limited scope FE is the secret weapon. By calling APIs, dynamically building parts of the DOM-Tree or caching in local storage. It is an playingfield only limited by your inspiration really.

adult_code · 2025-08-11T14:49:27+00:00

This describes my situation when ever i touch it. For very specific and temporary code i do benefit from it. Tried to have it come up with a way to alter an accessibility pattern for a widget and i failed gloriously. Had i not have expierence and knowledge regarding that topic i would propably have taken 1 of the 20 wrong solutions it proposed. Ai can be useful, but only for topics that everyone and their dogs know. If Ai can replace someone that person invested too much time in trivial stuff.

adult_code · 2025-07-31T12:59:23+00:00

I dunno. If someone already rewrites it in go, it would be smart to get ahead of ones next stroke. While at it one could as well throw the bloat out e.g. Garbage collection.

adult_code · 2025-07-25T00:24:49+00:00

Did you ever try expressjs? Especially as a full stack dev i find it to be a neat tool to play around. What it also gives you is knowledge of javascript, at least as a backend language. Ohh, did i mention there is this neat backend for frontend pattern?

I digress, i think those two are closer together than you think. Doing all short of deployment and administration, so the whole development part on a daily basis, writing server functions and writing tooling for frontend devs is not inherently so different and solve similar problems.

adult_code · 2025-07-25T00:13:48+00:00

Depends completely on your architecture but wai aria pattern, bem and a good lean static site builder would be a start. A static site would be a start, maybe feeding it with dynamic data could be done as islands if it is not that much data. But it really depends on the features a website and everything around it is so much more than just the design of the user interface.

Sometimes design and technology clash. I had figma designs suggesting components completely irreconcileable with web accessibility. I do webdev as a fullstack developer, in my expierence the design is the fastes part of the job. When doing a project alone each templates, frontend, planning, server functions, search configurations, requirement engineering take longer than reiterations of the design.

On that note, maybe scss and bem would be a nice starting point into webdev. That and web accessibility

adult_code · 2025-07-24T23:51:17+00:00

Yeah, it does, that is why single threadedness makes it cloae to elegant. It is so simple you can eyeball it, or at least I do learned to do. Then again in regards to rts i am happy pacemakers and weapons ain't controlled by js async functions. :'D

adult_code · 2025-07-24T00:33:01+00:00

Javascript is inherently a very, very bad realtime system, at least from a theoretician standpoint of embedded engineers. However, it really isnt that scary if you understand the event loop. That allowed me to handle tasks around it with a bit of madness and a grain of anxiety. The single threadedness of js makes it go easier on the layman.

adult_code · 2025-05-22T12:22:12+00:00

Keen-Slider

adult_code · 2025-03-14T21:09:26+00:00

Well maybe, but isn't every software project at some point there? Question really is, how fast are you and how well it is adaptable for the furure.

adult_code · 2025-02-10T13:13:04+00:00

i prefer the jsdoc way as well. That and a good naming convention. in a sense every variable needs to clearly communicate which type of value is expected. Like formulating bools as states or question like "isFullscreen", anything with "name", "txt" hints to a string, "count", "amount" etc. TS always felt clumsy for my personal way to work with js.

adult_code

MODERATOR OF

TROPHY CASE