Sr. Software Engineer

i am a senior in highschool and i want to become a software engineer, my near college offers only computer science what should i do? I would love a guidance to the right decision

Asked by Elio Molina almost 7 years ago

I want to become app developer, applying now to http://themindpark.com/ . What should I write in cover letter to attract their attention?

Asked by julia over 8 years ago

is it possible to access locked content on desire to learn (d2l)

Asked by applebottom over 8 years ago

With a project management degree, can you become a project manager with no experience in the field

Asked by smiley over 9 years ago

I am sure it is possible but it would take some work and probably a good cover letter selling yourself. Asking a PM might wield a better answer though.

Hello, I've started to learn prog 9 months ago to create a felix clone
http://myfelix.software.informer.com/2.1/

an interactive window-less desktop-mate but I can't find a language that allows me to do that, any idea what language I should learn?

Asked by Bobijoe over 9 years ago

I am not sure about other languages, but I am sure C# has this capability. I am assuming it could be done with Windows Forms or WPF. I am not as familiar with windows form solutions but I know they have the ability to make parts of the form transparent, my best guess is that they did something around this but perhaps there is a graphics library that would better handle it while working with C#. There are tons of libraries out there to assist with all types of needs I would be surprised if something did not exists to aid you with this effort.

Found a link to assist: http://stackoverflow.com/questions/3017914/how-to-build-a-screenmate-programatically

What's the biggest misconception people have about your job?

Asked by JUpton over 9 years ago

It seems the government and others are on a big kick that "anyone can program" and they are trying to mandate programming courses into schools. I can slightly agree that sure "anyone can program" but working in the field seeing these "anyones" and their programming make me confident in my next statement. Just because you can write code doesn't mean you can write good code. This blog does a great job at pointing out some of the common issues developers have, some of them are just due to the mental capacity people have and their inability to think logically, there are other things as well and this site points out a few of them. http://www.yacoset.com/Home/signs-that-you-re-a-bad-programmer 

Another misconception I would say is that "You have to be a mathmatical super star" is completely incorrect. Sure if you cannot do basic arithmatic then you will struggle but you do not need to have triganoetry, physics and other advanced mathmatics to survive as a developer. Math is most important for game developers but if you are an application developer understanding PEMDAS and a basic understanding of algorithms will get you where you need to be. If you do stumble across a situation where you need a special algorithm thanks to google it is usually a search away.

When a company has a team of 10+ developers, are they usually working on the same codebase (and if so, how do they do it without stepping on each others' toes?) Or do they all kind of stay in their own lanes?

Asked by TM over 9 years ago

In my experience it seems team sizes are best set around 3-6 developers. Anything more get unruley. We use Source Control to help keep from stepping on eachothers toes. It does a pretty good job at helping merge code from develpers into a single code base but conflicts still happen and then you break into a manual merging process. Some source control types include Team Foundation Server, Git, SVN, and Mecurial. They all have their own pro's and cons. My personal favorite are TFS and Mecurial but I have worked with them all.

So the teams may consist of 3-6 developers then 1 - 2 Quality Assurance a Business Analyst and a Project Manager. There can be more or less rolls involved depending on the company and the project. In my experience usually a feature is given to 1-3 developers to work on while the others are working on another set of features which helps limit the exposure to conflicting code but it by no means completely eliminates the conflicts.

To directly address the question about working on the same codebase, technically we work on the same code base but use branches to make a copy of the source code to work on in our own area and once the feature is complete or to a state that is safe to merge back into the main branch the code it merged where other developers have access.