On 2025-03-24, bart <[email protected]> wrote:
When you have near-instant build times then it's completely different
way of working.
[...]
[ Dart / Flutter ]
Turns out what that refers to is that they want update times measured in **milliseconds*; that is, from the time a developer makes a change, to
that change being compiled, loaded in the live application and running.
On 24.03.2025 18:15, Kaz Kylheku wrote:
On 2025-03-24, bart <[email protected]> wrote:
When you have near-instant build times then it's completely
different way of working.
Obviously.
[...]
[ Dart / Flutter ]
Turns out what that refers to is that they want update times
measured in **milliseconds*; that is, from the time a developer
makes a change, to that change being compiled, loaded in the live application and running.
If that "subcultures in contemporary development" is (or becomes)
wide-spread or even standard... <shudder> - Software quality is
often already bad enough, no reason to foster that evolution.
Janis
[...]
Normally, fast turnaround improves the quality of software.
The worst case tends to be the one where devs stubbornly follow
original plan.
On 24.03.2025 22:06, Michael S wrote:
[...]
Normally, fast turnaround improves the quality of software.
The worst case tends to be the one where devs stubbornly follow
original plan.
This sounds as if you've never programmed in professional contexts.
Janis
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 160:02:38 |
| Calls: | 12,094 |
| Calls today: | 2 |
| Files: | 15,000 |
| Messages: | 6,517,761 |