How long long is your total time in Project Setup HELL
-
Not quite sure what you mean... Open up Visual Studio (or Eclipse, or what-have-you), click 'File -> New project', if applicable choose the template of your choice, et voilá! Takes about 5 minutes on a slow computer. I guess that's not what kept you busy for an entire day (or I've got some bad news for you...).
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}I see you marked his post with 'NoEffort' and 'GimmieCode' :laugh:
-
I see you marked his post with 'NoEffort' and 'GimmieCode' :laugh:
-
Yoda Bytes wrote:
I tried the for my WHOLE first day of employment to setup that project and went home as a failure.
Are you saying that you couldn't finish because it was a lot of work, or that you kept getting it wrong and having to restart? Either way, it's nothing to quit over -- unless, of course, you fed them a lot of bull during the hiring process. I need more information before I can call you an idiot with conviction!
I wanna be a eunuchs developer! Pass me a bread knife!
BOTH ARE TRUE. And I can be convicted with conviction of possessing the intellect of a converted convict.
-
What do you mean by project setup, exactly? I don't think anything with the word "project" in it, takes less then 8 hours; just guessing. :) If you are quitting after the first day, I would question that motivation first, before your skill set for "setting up" a project. You don't make it in this business, by quitting. Just saying...
From when you receive the project until when you run the project. Should I just expect the bag of files I'm given to actually run right the first time?!
-
Not quite sure what you mean... Open up Visual Studio (or Eclipse, or what-have-you), click 'File -> New project', if applicable choose the template of your choice, et voilá! Takes about 5 minutes on a slow computer. I guess that's not what kept you busy for an entire day (or I've got some bad news for you...).
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}Maybe he's talking about a C++ project in Visual Studio. All the libraries and linking and everything can become terribly difficult. I remember back from the days of VC++ 4,5,6 etc. It can be a real wormhole you fall into, trying to get build order and all that. It's far more difficult than the C# stuff. I'm saying this as a C# dev.
-
I assumed he meant the time it takes to install all of the required third-party libraries, configure the IDE, etc... Essentially the time between pulling the code from the repository and being able to successfully compile it. Visual Studio makes that really easy...
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)Ah, I see. Well, if he inherited a mess, then it most likely could take a day or two, at least, to sort things out. However, nothing to quit over.
-
I fancy myself a 'good' programmer, as do most employed coders i suppose. But one thing that being a good programmer doesn't make you good at is setting up projects. I actually had to turn down a job as the 'sole web programmer' at a makeup start-up because I couldn't setup the project in 8 hours. I tried the for my WHOLE first day of employment to setup that project and went home as a failure. I was too darn ashamed too return the next day and give another hopeless attempt. So as I am in setup HELL with this dang nabbit c++ and starting a new HELL MODE, I just want to know how much time would yall estimate you've spent in Project Setup HELL? 50 hours lifetime total is my estimate.
New project - 2-3 hours for silverlight/wpf but then we have been working with our framework for 4-5 years. Taking over someone else's code can take forever, especially if the source is crap or you have limited knowledge of the tech used. Quitting after 1 days effort is well... rather sad, unless you have recognised that you are incapable of doing the job.
Never underestimate the power of human stupidity RAH
-
I fancy myself a 'good' programmer, as do most employed coders i suppose. But one thing that being a good programmer doesn't make you good at is setting up projects. I actually had to turn down a job as the 'sole web programmer' at a makeup start-up because I couldn't setup the project in 8 hours. I tried the for my WHOLE first day of employment to setup that project and went home as a failure. I was too darn ashamed too return the next day and give another hopeless attempt. So as I am in setup HELL with this dang nabbit c++ and starting a new HELL MODE, I just want to know how much time would yall estimate you've spent in Project Setup HELL? 50 hours lifetime total is my estimate.
Once my Eclipse IDE said some of jar files are corrupted , I was not able fix the problem after a day. I then formatted the PC and reinstall all the stuff again, it took me 2 days to get the workspace working. I hate those freaking classpath that are scattered throughout of my computer.
-
A week and a half. Java/GWT with about a dozen different internal and third-party frameworks all cooperating and competing. Really makes me appreciate Visual Studio and C#/.NET... Granted, it was my first time using a Java IDE in over ten years, but still... EDIT: Oh, and sorry, that's not lifetime... That's one project.
Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)I have the exact same experience with GWT. No matter what third-party library you use, at some point it will be deprecated. I never understood why we're using that stuff in the first place. (I'm a C#/.NET junkie) Recently, we tried to switch to Vaadin. (Sort of GWT with a shell) When installing it, we followed every step laid out on the website, then I create a new project: errors! Red squigglies all over the place. Just by creating a new project! Never mind that stuff. Java and everything associated with it is dead to me. C#/.NET/Visual Studio all the way! The phrase 'It just works' is so true.
-
I have the exact same experience with GWT. No matter what third-party library you use, at some point it will be deprecated. I never understood why we're using that stuff in the first place. (I'm a C#/.NET junkie) Recently, we tried to switch to Vaadin. (Sort of GWT with a shell) When installing it, we followed every step laid out on the website, then I create a new project: errors! Red squigglies all over the place. Just by creating a new project! Never mind that stuff. Java and everything associated with it is dead to me. C#/.NET/Visual Studio all the way! The phrase 'It just works' is so true.
Yeah, had kind of same experience. That's why in our dev platform we pay a lot of attention to this "Project Stetup" step. I would appreciate you check it out and share your view on what we do [^]. From my perspective if framework cannot be launched in 10 mins then just f*ck it and move to another one. So, this idea is one of the fundamentals ones, that stands behind the CUBA Platform
