Hacker News new | past | comments | ask | show | jobs | submit | neocron's comments login

I somewhat agree, but I don't use tools like copilot integrated into my IDE at all (tried it in beta) and I just hate that the suggestions it made were even worse than what the IDE suggested before. It was kinda what I wanted but like you said with small errors that were hard to findy because mostly it was working.

But what I reall like is using stuff like edge copilot and other chat-like ai tools to just ask questions and get some, mosty really well, summarized answers. Usually about tech I never used before, haven't used in ages or need to be migrated to much newee versions with breaking changes.

It saves me a lot of reading the docs, fiddling with it, reading the docs again, reading quite a few posts about it e.g. on stack overflow and than finally getting to work on the actual project.

I just ask my questions, try the suggested approach, fact check the docs and get to work


Whats wrong with using a CMS? A lot of them offer html content elements if you wish to express yourself more freely

I don't miss the days of framesets and including the header, footer and menu over and over again


A CMS makes the backend inaccessible. Want to add inline styles to a page? You can't. Want to embed a script for some quick interactivity? You can't. Of course you could attempt to locate the theme files and edit them, and edit the configuration files to enqueue scripts but at that point you're no longer having fun.

The only thing you can do is write paragraphs in templated portions of the page. And that's who a CMS is for: people who are doing a job, and have no curiosity about looking under the hood and messing around.


That's not my experience working for CMS like TYPO3 for many years. Although actually using that power without proper training for the editors often results in chaos.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: