Tim Moores wrote:This takes it a problematic step further, though, as contributions to some political organization would likely be indicative of voting behavior - which is supposed to be secret.
J. Kevin Robbins wrote:I've never noticed anything like this before. Is this becoming the norm? How can they legally use your political contributions to determine employment eligibility?
Jayesh A Lalwani wrote:On the other hand, your job in a Microsoft ecosystem is easy: You use the tool that Microsoft gives you, and you know everything will work together. If the tool doesn't do what you want it to do (or makes it difficult), you shrug your shoulders and say something about technical limitations or such. You can squarely put the blame on Microsoft's shoulder and Microsoft is more than happy to take that blame. They get a good excuse to sell your company the next version of Visual Studio.
If you are in a Microsoft stack, you aren't competing with other companies like you on the strength of your developers or technology choices. You are competing on how well you can manage your projects.
Jayesh A Lalwani wrote:I see being able to design good software as a skill that is orthogonal to converting design into code. You don;t need a 4-6 years degree from an engineering school to write good code. You need that degree to do design and solve problems. We need engineers to do the design.
We need coders to do the code. Right now, we take engineers and all they do is code, which is a big waste of their engineering degree
I'm talking about engineers focusing on solving the hard problems and doing the design while coders do the grunt work Right now, I can have a developer bang out a REST service using Spring pretty easily. I can have another Java script developer consume that REST service produce a good looking UI.
I, as an engineer, can focus on the design aspects, the DB design, designing the interfaces between the UI and the REST service, sizing out the architecture for scalability and efficiency, etc, without writing a line of code. I can do all the "figuring out". I use engineers to bang out this code. Why do I use engineers? Because that's what is available. These guys can do a lot more. It's a waste of their education. I could use coders who are trained in bootcamps to do the same job.
Right now, in the IT industry we train people to be construction engineers and then ask them to do plumbing jobs. Then the engineers cannot do plumbing jobs because they haven't had too much experience swinging a wrench in school, we send them to wrench-swinging "bootcamps". Then people who have never gone to construction engineering school show up and learn how to swing wrenches as well as the engineers, we sneer at them because that's the only way we can justify the education loan.
Jayesh A Lalwani wrote:I think there are pros and cons to this. Bootcamps might teach you how to bang out code. They can't teach you how to do it the right way. They can;t teach you how to design. They can't teach you how to write maintainable code. More importantly, they can't teach you how to learn. The biggest advantage that a CS related university degree gives you is that it teaches you enough fundamentals that you can start self-teaching after college.
What we need is people who can bang out code, which is what bootcamps provide.
We have plenty of engineers who do technicians work. Seriously, do you need a 6 year degree to write a CRUD web app? If all you do your entire life is make CRUD web apps in one language, then your 4-6 year degree is a waste. A kid could do that after attending a 3 month bootcamp in web development!
S/he may not know how everything works, but is able to put things together, in much the same manner as your plumber may not really know what went into the design of your plumbing, but can put a sink together.
I think bootcamps are good. They generate coding monkeys. Coding monkeys are good. They allow engineers to focus on the bigger picture.
Jayesh A Lalwani wrote:some of the requirements didn't make sense. I asked the manager, and she said "Oh they guy we are trying to replace has these qualifications, so I put these things in there". She wanted someone exactly like the guy who had left, so she took his resume and turned it into a job requirement.
Jan de Boer wrote:But, I had a year contract. I had a talk. The present year contract will be finished on the 15th of July. I heard criticism, and I now got a half year contract. (Until January 2015) My reaction, emotionally perhaps, but, I am going. That is the first conclusion. My only doubt is, should I go now, or after half a year?
I am actually pretty sure that after this contract they will fire me.
I know this is subjective, but, if you had a year contract, they should at least offer you another year contract.
This together with the criticism, make me conclude that I should go. The other bad thing here, is that I am not really a success story lately.
And I already got two rather short stays.
Jan de Boer wrote:I state that English spelling rules are that ridiculous, I think at least a few errors can be ignored.
Jan de Boer wrote:But the thing is that you either 'go' or 'no go', also towards the candidate. You do not plan a second interview three weeks later, and then three days before that interview you say: 'Hey, we just talked about your application internally and decided not to invite you for that already planned interview'. I think it's not well organized. Talk about the first interview internally first, and then 'yes' or 'no' invite me for a second.
Also, I am not sure how it is in your country. But I have never had a second interview without a job offer. So having a second interview for me, normally means a really high chance of getting hired.
Devaka Cooray wrote:Open source are not meant to earn money from them. People who contribute in open source do so with the prime interest they have in open source, and not as a way of making money.
Ram Nagaraj wrote:What I would like to do is handle a part of employee benefits myself say paid time off, medical insurance, 401k etc instead of allowing my employer to handle that so that I can demand a better hourly rate.
As far as taxes are concerned I want employer to take care of that (say fed/state/city social, medicare etc...)
So keeping this in mind what is the billing rate one can expect for a senior developer position?