System -> Advanced ->
-> For developers -> Developer Mode [on]
-> Dev Drive -> Create Dev Drive492 karma · joined July 21, 2010
System -> Advanced ->
-> For developers -> Developer Mode [on]
-> Dev Drive -> Create Dev DriveThere is a lot buried in this question but it can help sus out if the rules in place allow the challenges the system faces today or if it is antiquated in how it views the world it operates in. Good and bad can be related to time and context but like many things in software, it needs to be able to change and sometimes that change requires the willingness to start from scratch with new assumptions.
Attributes like mix of languages, system/task ownership, specialization are symptoms that an architecture may want to enable or discourage but are symptoms, not measures of quality. Automated testing and how much that influences your software design is more aligned with the culture of the organization and how it treats code than it is the arrangement of subsystems it is built on.
I use intelliJ for much of my development and also set the built in AI tools to use my GLM sub (BYOK) and it has worked out well albeit a bit slow.
Overarll, it's my main model and has been getting better with each release.
In order of overriding priority
1. Obey the Law 2. Support our members 3. Support our employees 4. Support our suppliers 5. If we do the above, we'll reward shareholders
I feel that new is wasted on me because I'm not confident that my own thoughts on what's interesting and worth front page promotion is well... interesting to the community.
Rounded corners still seems to be the unending trend through that anything that wasn't already well defined gets infected with.
I setup entire virtual teams (Dev, QA, product, reviewers etc with the initiating model just acting as the agent manager to keep it's context minimal) to one-shot some stuff and it kept churning and making progress.
Those days are just about over with the change to token pricing but for a time....
For example. page content of a PR with open comments, next action is to focus on the first comment. when a new PR with no open comments is shown the approve/push button is the next action. That starts a re-enforcement loop.
A project like this is to have a fun experience in a vehicle that was never designed to drive with electric qualities. I don't need the most efficient vehicle for my use so I could afford to trade some of that for fun. I'd probably try a Subaru Impreza STi because it would just be a blast to have a car of that size and stature with an electric powerplant under the hood (or trunk, or wherever it fits)
// I jest... but only to hide the sadness
The two primary OS items that turn me off of zed are not being able to have a title bar and the fact that menus open on hover and not on click.
VSCode, and IntelliJ let me turn on OS level title bars so I can handle the window without needing to try and find the magic spot not filled by some other app based nonsense as well as making it easier to see what window is active.
Menus can be unrolled from the hamburger but now pop open if I just swing my cursor through. I've no idea what convention that was pulled from but I think they just took the hamburger menu event triggers and left them as they were instead of changing them to act like an OS menu is expected to function.
I'm sure there are others that I'd find using the app but just those two was enough of a personal issue for me to just not bother.
The deal is really pretty much garbage now and I believe that is the intent.