I agree, I rather take my chances with a modern JVM and probably apply some fixes than have it completely broken for an unknown version of javascript and whatever the browsers of the future will think what HTML5 should look.
Agreed... programing is a tough mental activity that is hard to define how it works.
On a side note (after reading your link), I hate idolizing good programmers (maybe I'm not one of them) because sometimes it gets to their heads.
Actually good programmers should NOT last long working in the same company. They should mentor, educate, leave clean self (not obfuscated) documenting and modular (elegant?) code behind.
At one point he will know it will be time to move on to bigger things but leaving behind a great legacy of work. How many times teams have to redo code because they can't make head or tails of the blob of code that some idolized programmer left without a hint of what he was thinking.
Software development IS HARD... writing code requires your brain to be working, abstracting and problem solving at 100%. Thinking of doing that everyday for months takes determination, discipline, passion, insanity or a mix of all those.
For some reason the software profession has lost the recognition and respect it deserves, part of the fault comes from the same developers that agree to anything without regard to timelines or effort required. If they could have some self respect and say "no" a couple of times I bet software will stop becoming a commodity anymore.
For management to surrender control (specially in big projects) means a huge deal of trust.
That seldom happens in big projects where huge amounts of money are involved. When this happens the issues are more political than technical, so Agile helps management take a peek at how things are going. It forces developers to communicate which takes time and effort away from coding.
Unless there is some other way of letting developers hide for months and making management feel good about spending money with nothing to see for months and months.
A team of nine women will deliver a baby. ONE woman is the critical path and she will not stop with her one job of making the baby until she is done. The other eight women will: - take care of feeding her, - taking her to the doctor, - making sure she is healthy and eating a good diet, - paying her bills, - buying everything for the new baby, - making sure she is keeping up with family and friends, - helping her prepare for the birth with respiration and pushing exercises, - making sure she is recording everything in pictures and video.
- Plan for fairly frequent milestones where you can build a release (that runs with bugs but it has something to show of how the system will work when completed). - Be able to test new and old functionality by being consistent in building useful unit tests. - Be able to say what you will be doing in the next couple weeks (or months even) and somehow you are able to deliver on that.
In essence having a loop where you at least touch with some new code most of the functional areas of the system.
Otherwise you might say "the database layer is complete but I can't show you until the business layer is done and that will be probably done in six months..." Management will go nuts trying to figure out what to tell their bosses while still justifying the expenditure with nothing to show for in months and months!
- Read, study and practice Agile so he/she can "truly get it". - Understand the big picture and learn how eventually the final product fits into the user's needs. - Take decisions and follow through with them.
Agreed, agile in the sense of managing change. It doesn't focus in the speed of how you work.
I think is keeping your mind open and expecting expecting change (i.e. lots of refactoring), the methodology should account for the amount of time it takes to do each task and is up to you or the team to decided what is more important to work on next.
Be prepared to throw away lots of code and refactor it into smaller or more modular units. If you don't you will quickly slow down trying to deal with patching an earlier model.
And... take what is useful from Agile and ignore those things that get in the way.
Yeah, it has to be a little more subtle... not making the user feel that he/she has done something wrong and feeling at risk (we are talking html rendering here)...
If it sucks so much then fortunately we are not forced to buy it. I don't own an iPhone and don't have a burning desire to own one. So reading this is kind of entertaining.
$30 dollar phone with pay as you go airtime for the win.
Don't set your hopes too high for this to become accepted as regular speech.
It will just be another filter to socially determine if you have "acceptable" social skills and manners compared to being part of the masses.
Gook luck talking like that in your job interview, your client's presentation or even on your first date. Speaking like a sailor will only damage your first impression. Make sure you know when and to whom to say it. When in doubt speak like a prince instead.
You might later discover that your client or your girlfriend speak worse than you BUT if they don't you could have royally f****ed up your chances.
Well said and I get that it's difficult to describe what programming is.
I read that programming is like writing music; you have a team of musicians that form a team to plan for the theme, score, composition and lyrics of a song. Basically they follow a plan and build gradually, adding complexity and leaving their style on the final product. There are of course the rock stars that compose a hit song in the back of their tour bus when traveling between concerts. But you can't count on that divine inspiration every time you want to produce a new CD.
What programmers have to do is keep upgrading their skills, just like medicine, you don't want your doctor to avoid using the new techniques and drugs just because he refused to update his knowledge. The extreme example here is the COBOL programmer, yes they work with very old tools but they should at least know what the latest trends in the industry are and not fight against them.
What is probably true is that learning new things as we get older becomes painful as our prejudgments get in the way. We old timers forget that learning is something playful that helps us absorb and retain it painlessly.
My advice is ditch the rebellious hacker look and join the acceptable dress code like the rest of the other professions. Learn to offer your skills professionally, communicating what services you provide. This might require you to talk to people, be polite, listen to customers needs and offer deliverables on a timely manner.
Ditching experience would be unheard of in medicine, engineering, law, carpentry, pluming, construction, etc, etc, etc.... But only us have the balls to say that youth trumps experience, I wasn't aware kids were born with all computer science concepts from the get go.
How is it that a senior programmer ends up in sales?
Maybe we are not taken seriously because our professional low self esteem.
Slashdot Mirror
+1
Not bad indeed, having both cameras and faster graphics is what I like.
I agree, I rather take my chances with a modern JVM and probably apply some fixes than have it completely broken for an unknown version of javascript and whatever the browsers of the future will think what HTML5 should look.
I'm very happy with AVIRA as well.
Small memory footprint and efficient.
Recommended!!
Agreed... programing is a tough mental activity that is hard to define how it works.
On a side note (after reading your link), I hate idolizing good programmers (maybe I'm not one of them) because sometimes it gets to their heads.
Actually good programmers should NOT last long working in the same company. They should mentor, educate, leave clean self (not obfuscated) documenting and modular (elegant?) code behind.
At one point he will know it will be time to move on to bigger things but leaving behind a great legacy of work. How many times teams have to redo code because they can't make head or tails of the blob of code that some idolized programmer left without a hint of what he was thinking.
Ummm... you lost me why cracked, rotten eggs.
Software development IS HARD... writing code requires your brain to be working, abstracting and problem solving at 100%. Thinking of doing that everyday for months takes determination, discipline, passion, insanity or a mix of all those.
For some reason the software profession has lost the recognition and respect it deserves, part of the fault comes from the same developers that agree to anything without regard to timelines or effort required. If they could have some self respect and say "no" a couple of times I bet software will stop becoming a commodity anymore.
OO fiasco? So go back to procedural code?
For management to surrender control (specially in big projects) means a huge deal of trust.
That seldom happens in big projects where huge amounts of money are involved. When this happens the issues are more political than technical, so Agile helps management take a peek at how things are going. It forces developers to communicate which takes time and effort away from coding.
Unless there is some other way of letting developers hide for months and making management feel good about spending money with nothing to see for months and months.
Is more like:
A team of nine women will deliver a baby. ONE woman is the critical path and she will not stop with her one job of making the baby until she is done.
The other eight women will:
- take care of feeding her,
- taking her to the doctor,
- making sure she is healthy and eating a good diet,
- paying her bills,
- buying everything for the new baby,
- making sure she is keeping up with family and friends,
- helping her prepare for the birth with respiration and pushing exercises,
- making sure she is recording everything in pictures and video.
Agreed but... you should be able to:
- Plan for fairly frequent milestones where you can build a release (that runs with bugs but it has something to show of how the system will work when completed).
- Be able to test new and old functionality by being consistent in building useful unit tests.
- Be able to say what you will be doing in the next couple weeks (or months even) and somehow you are able to deliver on that.
In essence having a loop where you at least touch with some new code most of the functional areas of the system.
Otherwise you might say "the database layer is complete but I can't show you until the business layer is done and that will be probably done in six months..."
Management will go nuts trying to figure out what to tell their bosses while still justifying the expenditure with nothing to show for in months and months!
What he said... I'm reading up on Spring and so far nowhere does it says that code will be auto-generated.
A good framework will allow you to implement manually as well as using the library and packages.
Any mortal can:
- Read, study and practice Agile so he/she can "truly get it".
- Understand the big picture and learn how eventually the final product fits into the user's needs.
- Take decisions and follow through with them.
Agreed, agile in the sense of managing change. It doesn't focus in the speed of how you work.
I think is keeping your mind open and expecting expecting change (i.e. lots of refactoring), the methodology should account for the amount of time it takes to do each task and is up to you or the team to decided what is more important to work on next.
Be prepared to throw away lots of code and refactor it into smaller or more modular units. If you don't you will quickly slow down trying to deal with patching an earlier model.
And... take what is useful from Agile and ignore those things that get in the way.
Agreed hahaha!!
My (blank) ???
Yeah, it has to be a little more subtle... not making the user feel that he/she has done something wrong and feeling at risk (we are talking html rendering here)...
Nice.. well at least I see you were modded 5-Funny.
Otherwise you were doing your profession a disservice.
Video has been removed, that could be a story in itself...
If it sucks so much then fortunately we are not forced to buy it.
I don't own an iPhone and don't have a burning desire to own one. So reading this is kind of entertaining.
$30 dollar phone with pay as you go airtime for the win.
It might be so but coming from DEBKA I would look for some confirmation.
After all they have somewhat of a little bias against all of the middle east.
It was DEBKA who was reporting an imminent war this past summer involving the US, Iran, Israel, etc.
If you can confirm their reports with, I don't know, AlJazeera maybe then we can say the news is quite legit.
They do make for great reading though.
Don't set your hopes too high for this to become accepted as regular speech.
It will just be another filter to socially determine if you have "acceptable" social skills and manners compared to being part of the masses.
Gook luck talking like that in your job interview, your client's presentation or even on your first date. Speaking like a sailor will only damage your first impression.
Make sure you know when and to whom to say it. When in doubt speak like a prince instead.
You might later discover that your client or your girlfriend speak worse than you BUT if they don't you could have royally f****ed up your chances.
Wouldn't using GMT free you from time zones and seasonal time saving changes?
umm... I think you are confusing civil engineering with architecture.
Well said and I get that it's difficult to describe what programming is.
I read that programming is like writing music; you have a team of musicians that form a team to plan for the theme, score, composition and lyrics of a song.
Basically they follow a plan and build gradually, adding complexity and leaving their style on the final product. There are of course the rock stars that compose a hit song in the back of their tour bus when traveling between concerts. But you can't count on that divine inspiration every time you want to produce a new CD.
What programmers have to do is keep upgrading their skills, just like medicine, you don't want your doctor to avoid using the new techniques and drugs just because he refused to update his knowledge. The extreme example here is the COBOL programmer, yes they work with very old tools but they should at least know what the latest trends in the industry are and not fight against them.
What is probably true is that learning new things as we get older becomes painful as our prejudgments get in the way. We old timers forget that learning is something playful that helps us absorb and retain it painlessly.
My advice is ditch the rebellious hacker look and join the acceptable dress code like the rest of the other professions. Learn to offer your skills professionally, communicating what services you provide.
This might require you to talk to people, be polite, listen to customers needs and offer deliverables on a timely manner.
Ditching experience would be unheard of in medicine, engineering, law, carpentry, pluming, construction, etc, etc, etc....
But only us have the balls to say that youth trumps experience, I wasn't aware kids were born with all computer science concepts from the get go.
How is it that a senior programmer ends up in sales?
Maybe we are not taken seriously because our professional low self esteem.