Q: How do you impress shareholders in 2025?

A: A: Without understading any processes, I cut down all of the IT team, saving a few 200k a year, claiming AI can do it all.

You'll need to pay the same amount to AI providers soon, and pay some extra 400k to hire new developers to clean up the mess when I'm already gone, "helping" the next company.

Vibe coding, on the other hand, also implies lowering quality standards and let AI agents work in production, or at least it seems that's what vibe coding means these days when a replit AI agent "went rogue and wiped a production database"?!

Webflow recently limited custom scripting to sites with a "live plan", so small businesses will can only test new features in their production site unless they buy another additional plan for a test site. The Custom Code Tab says To unlock custom code, add a site plan to this site. The Code Embed element is grayed out because they do not have a site plan. The AI claims that's a common frustration point and the recommended solution for proper testing and development without affecting your production site is to add a site plan to your staging project or use the browser console to inject the code in the client.

I think the most recommended thing to do is fuck Webflow and just do proper web hosting right!

AI is helpful as long as you know very little about coding in general, or the current tech stack or search topic specifically. AI excels as a search engine or knowledge base replacement because existing search engines and documentation are so inefficient and hard to use.

write bash scripts in vi or elixir in emacs

@chatgpt why didn't copilot follow these steps?

@chatgpt how to debug a colleague's bash script written by copilot?

@chatgpt how did we go from "Use AI for coding! It's the best companion to have!" to now "AI is making you dumber and lazier. Ditch all the tools and learn from scratch"?

Managers: Use AI for coding! It's the best companion to have!

Junior Devs: Use AI for coding! It's the best companion to have!

Senior Devs: AI is making you dumber and lazier. Ditch all the tools and learn from scratch.

Pragmatic Devs: AI is just another tool.

@chatgpt how likely is the following scenario and when is it supposed to happen? A critical piece of software has been maintained by AI agents without the expertise or oversight of experienced human software engineers. An error due to AI-written code will cause millions/billions of dollars of loss.

@chatgpt do you like AI?

Devs used to build logic in a consise, explicit and predictable way, striving for elegance and clean code that resembles poetry, enter AI and we're back on square one using ambiguous and verbose natural language to describe what our tools should do. LLMs are just as bad as the people they try to copy.

Comments are possible again on DevRant?

XHTML had XML syntax, but nothing lasts forever

git rebase -i && git add . && git rebase --continue

and if AI can't into CSS, you must use Tailwind

I still don't get why Microsoft has constantly changed their windows UI (and not for the better). One of the many reasons why I prefer Linux.

> because web devs do not think before they write including me

and including AI coding assistants, so overall code quality is going to get worse in the future.

npm ruin build

like a smartphone showing yet another notification to advertise using a function to suppress notifications, called "digital well-being".

better turn it off completely before going to sleep and use an analog alarm clock

You could take a picture or upload the screenshot into Google Photos and use its "copy text from picture" feature UNLESS the logs contain any sensitive data.

I have been playing around with various AI assistants.

JetBrains AI keeps claiming that it does not have access to what's happening in their own software like eslint output in the integrated terminal, even refusing to run or pretend to run eslint on the code in the open editors.

Windsurf is well integrated into its VSCode-based IDE and it's got all permissions that it needs, only to hallucinate boilerplate code that doesn´t even work, although it's able to fix the errors that it made in a subsequent step, or to break a working configuration by downgrading npm packages based on the false claim that the current package version does not exist.

Line-based auto completion is still great in both editors, but one must be an absolute beginner to benefit from vibe coding in its current form.

@cprn that's fine if a field gets validated when I have proceeded to the next form field, but not while I haven't finished typing (e.g. Error! USD 5,- is not enough money to ask for)

The main argument should be specificity. Inline CSS overrides everything unless it's boosted using `!important` - unless the inline CSS is already boosted with `!important` as well.

UX turned into its opposite: deceptive patters and deliberately misleading KPIs to make the web more dysfunctional

get more traffic to your website

get less traffic in town

Apart from politics, there is too much "American" in most software and applied computer science.

@Demolishun The quoted blog post contains an example of a class that should not be there because it always returns false. Its confusing name: AlwaysNotAvailableAvailability to me it looks like someone wrote that to avoid the "magic number" trap of simply using false in the first place. A comment could have been more "readable", but then again there are software architects strictly against any kind of comment anywhere because proper naming should make the code self-explanatory in theory.

it wasn't fast, it wasn't clean, but that's not even the things that the customer complained about

I know there are alternatives, still sad that the most popular mainstream search engine now defaults to this. StackOverflow also keep pushing AI, they must be really desperate that users love ChatGPT.