Also unfortunately the problem lies when the platform has too much power and makes this relationship with the author disproportionate. At first such a platform seems like a good deal for everyone, except when it stops being one
Same here, the brainstorming and research phases are good and the spec part at well, I do side adversarial reviews all the time with other independent agents and feed sp the reviews and they are tools to avoid gliding over the surface. The dev process is longer but the result when done in a sound architecture with documented practices is quite good even though it’s slow.
Very happy with the tool so far
Oh wow so sorry to hear that, never thought taking about my insensitiveness to cafeine would yield such discussion. I’m not going through what you feel and I might never know if I save some form of ADHD or not.
Maybe there’s a bright side to it or at least some hope for things to get better with time. I deeply wish you the best and to find relief
Actually I’ve been inattentive as a kid and when I like something time stops I can have really deep focus. But I’ve learn to dig subjects I don’t like to succeed at school and at work so idk if I have ADHD. Sometimes I really hate what I have to do at work and it can be really painful to engage with it and I procrastinate a lot. But I guess many people are like that
Actually I never felt the need to be diagnosed with ADHD. So I just looked up online and at first-read I don’t think I have something particularly different that could classify me but I might be wrong. Pushing it I also read that there is genetic part to cafein sensitivity but my parents don’t drink coffee at all so I guess I’ll never know.
It’s not really a problem though, I can drink double espresso and take a nap or go to sleep which is nice. I can enjoy very good specialty coffee without trouble
I noticed from reading threads online that I can drink 8 espressos a day and stop having espresso for several days or weeks. I make my own from ground beans of 18g. It does nothing to me, I never felt a stimulation and only taste guides my need. If I don’t like the taste even offered in restaurant I will refuse to drink it.
I don’t know why I’m like that but I never understood the discomfort phases and the stimulation ones either. Idk if I’m missing something
At work there’s been a huge number of duplication in the start of the company and no solid abstraction. So no tests as well. We introduced tests in the current architecture but rewriting code has a huge cost to make sure there is no regression. When we talk about a saas it’s non-trivial with many customers relying on this tool daily as part of their workflow, regressions because of rewrite could be really painful for them. So we must give a greater budget to take the time to make sure nothing major breaks. So there is a debt that is compounding over time because code is added. Duplication is bad and weird/purist abstraction could make the architecture so rigid that rewriting things could generate hard to understand and catch bugs.
It’s hard to find a good balance and it depends on the kind of business and scale of project. Hard to make that a generic advice.
I noticed that is quite hard to make people change habits regarding software. There is shortcuts to learn and we might feel slow at first which reinforces the feeling of « it’s not better ». It takes a while to get used to nvim, once there it’s faster but that explain why many people stay in their confort zone
I agree, search in ClickUp is awful and it’s impossible to find back old cards from previous years. A nightmare. Plus, if consumes gb of memory in the browser.
I’m in a similar line of thinking and actually some customers are making their own version of our tool. It’s nowhere near feature complete but it suits their needs.
Code quality does matter it’s just marketing people being shortsighted because their job is to react to the market. LLM gives a sense of « it’s kind of easy to build stuff, why bother loosing time with quality when I’m there at 80% in 20% of the time ? ».
There is compounding effects where given any big enough system this won’t scale, even Google did talks this week on this topic. So I guess you’re right, time will prove who’s right or wrong and what bet was the best with which consequence
That’s exactly part of the feelings I have. I always loved to learn, dig subjects, debug, create. Now I feel something has been taken away and has no value. I feel indolence and apathy. In my company the CEO explicitly says that code quality does not matter. He doesn’t care as long as we ship fast and iterate.
I am genuinely sad and feel I’m losing something and if I do everything like I used to do, I am pressured that I waste time.
It’s a fragile equilibrium and it depends on the kind of project you’re working on. If the knowledge debt is ok then yes, it’s just like a delivery job, if the truck has an engine problem I won’t continue to deliver the packages by walking or finding and setting up an other truck from where the vehicle breakdown happens. I’ll just wait because the wait is still faster than the other solution because of the knowledge debt it’s too long to pickup by hand and continue.
Now if it’s my job then I can’t have a knowledge debt and if Claude is down I’ll continue working manually because I know and understand and can continue without having to understand a lot of logic before continuing
> It’s not lying. It’s not even wrong, necessarily. It’s just incapable of the thing that makes a real architect valuable: saying “no.”
In my workflows Claude does pushbacks all the time and justifies why. There is back and forth just like a colleague. It’s not perfect but the results are usually good
I thought the same and it depends on which context you work.
Below is an answer on slack from our CEO when I said talking about Claude code source leak : « Dirty, un-architected code is the new norm; it makes billions, who cares… »
He answered:
> Well, yeah, who cares?
> This is where we need to differentiate between what truly needs to be clean (critical APIs) and where some random guy coding a product in a week will wipe the floor with a team of engineers with a clean architecture and no product after three months.
> What's more, this "vibe coder" is on the right side of history… Who's to say AI won't be able to just rewrite the code cleanly while keeping the core idea within 6, 12, or 18 months?
> This is also the question that drives business... and in business, "good enough" has almost always trumped "perfect." Except when you're making an ultra-luxury product like a Ferrari or something. Which software almost never is (if ever).
So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.