use of build time
-
It is time you to move on to some serious project... To check a simple feature the build is instant, but a full version build is almost 15 minutes - fortunately it is done on a build machine so I have time to do other things on my computer...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
I don't think I want to work on those kinds of projects X| I have 5 minute builds, but only on the build server, those are still instant on my machine. Most of those five minutes are downloading NuGet packages anyway. I've worked with longer builds in the past, but those were mostly badly designed applications or multiple services in a single repository. For one project I had a really long local build, like 30 seconds, and I don't think I've ever figured out what the problem was :~
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
I consider it a non-issue. If you have a proper IDE and build system, and not the least: a well designed project structure, you modify and develop your submodule with incremental compilation and linking of that submodule. Absolute rule: You never commit any code that is not syntactically correct or violate coding rules (lint style, or whatever you use for static code analysis). If your system is well structured, and your tools are good, you might spend the time having another sip of coffee, not much more. Good rule: The commit process includes running basic module tests - a subset that runs through all relevant functions of a 'normal' code run, although not with the full set of all corner case inputs. So you commit your code, knowing that on the build servers, it will not cause any syntactic errors, and no logical errors for the standard usage cases - at least not at the module level. What do you do? You go on to the next issue to be handled. The next bug to be fixed, or next extension to be implemented. If it turns out that the complete project build causes errors that are not of an integration kind, then you certainly should have a look at your tool setup. That shouldn't happen. Even for lots of integration issues, usually a lot could have been detected pre-commit. Details depend a lot on IDE/build tool details. And, of course on discipline within the development team, e.g. regarding header files, if you use such a language. Treating interface definitions as immutable. Things like that. I am not talking about common practice. More like an ideal. But 'best practices' working habits can get you quite close.
-
This is one of the reasons every time I quit smoking its coding that gets me started again. Especially now that I don't have to worry about build times anymore because my machine is so fast, but I have to upload megabytes of firmware code via serial UART at only 921600 baud every time i make a change or two. That gives me just long enough of doing nothing that a smoke break is perfect. This is going to be the death of me. :~
Real programmers use butterflies
-
It is time you to move on to some serious project... To check a simple feature the build is instant, but a full version build is almost 15 minutes - fortunately it is done on a build machine so I have time to do other things on my computer...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
The question is: Have you made yourself dependent on the results of that 15 minute build to go on with your next task? If you deliver a submodule that is syntactically correct, passes basic (read: fast) module tests, and honors all external interfaces, chances are that the best you can do is to go on to the next bug fix or functional extension, without waiting for the system build to tell you that everything is OK.
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
[xkcd: Compiling](https://xkcd.com/303/)
cheers Chris Maunder
-
This is one of the reasons every time I quit smoking its coding that gets me started again. Especially now that I don't have to worry about build times anymore because my machine is so fast, but I have to upload megabytes of firmware code via serial UART at only 921600 baud every time i make a change or two. That gives me just long enough of doing nothing that a smoke break is perfect. This is going to be the death of me. :~
Real programmers use butterflies
-
Technically I've switched to vaping. I hate the smell of cigs, and vaping scares me so i was hoping it would keep me from doing it long term. Time to quit again. :~
Real programmers use butterflies
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
PaltryProgrammer wrote:
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
Coffee machine.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
At 3.4 Ghz and 16GB, there is little build time. UWP packaging and the Windows App Cert Kit (4 platforms) takes longer; long enough to make coffee.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
I read Codeproject of course!
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
Someone Else's Problem.
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
Why don't you spend that time writing a document for management? Rather than compiling locally It might be cost effective for your employer sets up a build server. That way you can continue coding while your project builds on a remote server. Best Wishes, -David Delaune
-
The question is: Have you made yourself dependent on the results of that 15 minute build to go on with your next task? If you deliver a submodule that is syntactically correct, passes basic (read: fast) module tests, and honors all external interfaces, chances are that the best you can do is to go on to the next bug fix or functional extension, without waiting for the system build to tell you that everything is OK.
trønderen wrote:
Have you made yourself dependent on the results of that 15 minute build to go on with your next task?
Absolutly not... That would be a disaster... The big build initiated when someone aprove a pull request an it blocks noone and nothing... I can move to the next task or even more take a break :-)
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
That depends on what project & what platform. The stuff I work on in Delphi or C++ builds fast. With precompiled headers for C++ anyway. Without them, I might just as well go back to my company's DOS-based product which I also maintain. I got this witty comic printed & glued to the side of the monitor attached to that DOS-based system https://xkcd.com/303
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
"build time"?? emm... are you building on PC XT or use punched cards? :)) I use C# in VS2019, my "build time" barely exceeds 2-3 seconds. What I do during that priceless time? Oh, I can breath 1-2 times. :) I'm absolutely serious and I still have no idea HOW you can build smth for minutes. My rule: ONE current project + referenced DLLs. If I improve two projects - OK, both of 'em include in solution. But even in that case all compilation is quite quick to do smth else.
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
Some of the things I do: - watch the (short) video I've been waiting to watch (eg from [Smarter Every Day](https://www.youtube.com/user/destinws2) or [She's Got Legs](https://www.youtube.com/channel/UChk1S9wy0pQY24zOUIQ2hUA) ) - solve a problem in another project (eg if there's an issue or just something I want to implement in one of my personal projects) - check up on Twitter You could also use the time to listen to a section of an audio book (eg from Audible) - I tend to use my Audible book time during commutes & garden work. The trick is being able to find something that you can switch to for that time which doesn't run over or dramatically pull you out of the focus you need to complete your current task. If possible, as mentioned elsewhere, move on to the next task.
------------------------------------------------ If you say that getting the money is the most important thing You will spend your life completely wasting your time You will be doing things you don't like doing In order to go on living That is, to go on doing things you don't like doing Which is stupid. - Alan Watts https://www.youtube.com/watch?v=-gXTZM\_uPMY
-
It is time you to move on to some serious project... To check a simple feature the build is instant, but a full version build is almost 15 minutes - fortunately it is done on a build machine so I have time to do other things on my computer...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
What is "serious" project? The place where you drop billion classes and believe it will work? :) Man, I made "serios projects" like security system for access control (fingerprints, face recognition, NFC cards, locks, zones, etc). There was enough code, but hell... none of my projects compiled above 3 seconds! Maybe because I used C# ? :) Pity C++ boys... they use ugly language with ugly ideas in compiler and have to wait minutes on elementary projects.
-
What is "serious" project? The place where you drop billion classes and believe it will work? :) Man, I made "serios projects" like security system for access control (fingerprints, face recognition, NFC cards, locks, zones, etc). There was enough code, but hell... none of my projects compiled above 3 seconds! Maybe because I used C# ? :) Pity C++ boys... they use ugly language with ugly ideas in compiler and have to wait minutes on elementary projects.
In this context 'serious' was there to pull OP's leg... This project has C# and JavaScript and made of several steps, the most time wasted on the Angular compiler (2/3) and on the minifing/combining process of JS and CSS... The big project itself made of nearly 200 separate projects, and while on my local machine I may compile a handful the most (several seconds) the background build compiles all of them to create a homogenous build that at the end deployed to a test server...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
-
I don't think I want to work on those kinds of projects X| I have 5 minute builds, but only on the build server, those are still instant on my machine. Most of those five minutes are downloading NuGet packages anyway. I've worked with longer builds in the past, but those were mostly badly designed applications or multiple services in a single repository. For one project I had a really long local build, like 30 seconds, and I don't think I've ever figured out what the problem was :~
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
I absolutely agree. I have several programs ERP, Production (this one interacts with AutoCAD), Maintenance, Human Resources, a MySQL - MariaDB query browser,... and when working on one of them compiling time never takes more than 10 secs (ERP or Production). These two have close to 700,000 lines of code each. I have a Core I7 8 core 9th generation processor, 32 GB RAM, 6 GB graphic card (useless for compiling). When I am using my home laptop for the same task, its about one and a half minutes. So I think the time required for long compiling times are several things. The power of the developing machine; the number of lines to be compiled; the number of external DLL, .h,... to be linked, etc. But definitely, the machine is a VERY IMPORTANT one. My 2 cents.
Work hard and honestly and you will be rewarded by your own satisfaction.
-
Greetings and Kind Regards May I please inquire how you spend your time while your project is building? As for myself I twiddle my thumbs or watch a portion of a Star Trek episode or stream music or merely surf Cheerios
My projects don't take that much time to build, mostly due to a lack of unit testing.
