Hmmm. In five years over clocking geeks will be taking 10MV and pouring liquid nitrogen right into the head while solving PI with 1 billion digits. Sick!
How about going down to Toys R Us By a small toy chair. Rig it wit cupper wire. And then just zap the litle terrorist. Broadcast it national TV. And force all kids to watch it!/sarcasm
Or perhaps someone should sue the judge for Child abuse ? Im thinking that judge must be having a serious attention disorder to exploit a 4 year kid just to make headlines. How sick is that?
Hum..."that the new specification will greatly increase the 'attack surface' of HTML — providing more avenues by which malicious code can be delivered through the web"
What specification ??
"greatly increase the 'attack surface' of HTML"
Omg. sounds horrible to me:( Sounds like its gonna turn my browser into remote desktop with a blank password..oh shit!!
> The GUI is just the tip of the iceberg. It's the least important as far as overall functionality, but it's what everyone sees and reacts to.
True. So you have to be a good communicator besides being a good system developer. Often you have be good at smooching a litle bit too:) Unfortunately, in most cases, being good at your profession is usually not enough when you work with IT Thats is why you have to walk sometimes even thoug it can be tough. But you can plan for it and you can learn to become better at navigating through bad projects ( learning by doing:)
Pitching two developers, teams or even companies against each other maximizes your change of success. That is: 1. As management, you dont have a clue about what you are doing in the first place (go happy lucky) 2. You dont mind spending the cost two times over 3. To stay in power, You have learned to divide an conquer
But your cost will double Your employees will start fighting and sabotaging each other
1. Understand the business rules. You need to know what the system / application does before you can begin making changes to the code.
2. Get an overview of the system design / code structure. If there is any (otherwise it is going to be very difficult). Break down the system into use cases and try to see what part of the code each case covers. That should give you an idea of the business logic and the class structures (assuming it is not one big bowl of spaghetti).
3. Create a working document with your diagrams and development plans. Put all your observations on a whiteboard, paper or a napkin as needed. But remember to draw it Visio, Word or OpenOffice.Writer too. You don't have to do this all at once. It can be done as you move into the code to fix bugs or when making changes.
It will probably take you between 6 to 18 months to get fully acquainted with 30-40K lines of code. It also depends on how hard business is pushing you. The more pressure on bug fixing and system changes, the less time you will have to learn about the system as a whole. Even though 30-40K lines isn't that much it is probably more than a one man job. If it is a business critical system. It is more likely to be a 2-3 headcount. You should have you own exit strategy ready and get out of there, in case business wont take your challenges seriously.
Anyways i hope they pay you well. Good luck with it.
In a working environment a nice idiot will always be an 4hole, no matter how nice that person is. If you cant cut it, just get tf out of there. Nice is a compensation for not trying hard enough. It is often accompanied by a really good excuse. Leaving the problem to somebody else. Which in the end really isn't so nice. Because of their lack of skills and inherent laziness, nice people will often smooch their way into middle management positions. That is the reason why there is so many incompetent idiots in IT management positions. On the other hand A Rude person that is always right, is just person with a great personality.
Good enough.. Always depends on who you are asking. It also also implies that it could be better, admitting obvious shortcomings. The supplier will find it good enough when the product meets the requirement specs. The customer will find it good enough when the product actually supports the business process. The end user will (almost) never find the product good enough. Its just a matter of getting the contracts right. Dealing with large government projects, thats as easy as it is impossible:) The problem with good enough is that it colides with quality. And bad quality is always expensive in the long run. The supplier: Just be good at two things. Customer expectation management (do the talk) and Estimating/Developing (do the walk) The customer: You can't manage what you dont understand. So understand what you are dealing with. Alot of IT managers dont have a clue about IT at all, especially in the government sector.
If only MS would add support for SVG and CANVAS. Take a look at this comparison chart: http://www.naxos-software.de/blog/index.php?/archives/45-Interactive-Cross-Browser-Vector-Graphics-on-Top-of-SVG,-VML,-Canvas,-Silverlight-using-Dojos-GFX.html But MS is rather going for Silverlight as their answer to Flash. Just like that ASP.NET was MS's answer to the internet (it was not working). As of today Flash does the job while Silverlight might in a couple of years if ever. Never the less having to rely on third party plugins always sucks. . However thanks to initiatives like dojo gfx and others. It is possible to have drawing capabilities with DHTML and pure javascript. The approach is to wrap the current browsers supported drawing API like SVG, CANVAS or VML. Check the link below. See the Link section in above link. . A primitive but practical approach to get (simple) drawing capabilities is making your own drawing library that paints using the good old div tag. I know that it sounds ridiculous, but Walter Zorn have made a quite useful library, that some use for charts, diagrams, rounded corners etc. See below link. http://www.walterzorn.com/jsgraphics/jsgraphics_e.htm#performance . It would be nice if all the browser vendors would sit down and agree on a very simple drawing API, that would make it possible to draw polygons and primitives and do translations in a cross browser environment. And then compete on the more advanced plugins for those who need it (the add business who makes annoying banners). Right now the most experienced and stubborn developers can get around without having to bother with plugins by hacking their own libraries or using open-source alternatives. Over time libraries like dojo gfx will translate into new standard gfx API's that I guess will help MS to join the rest of the world and become part of the internet. . Someone please try to talk some sense into MS next time you meet:) Just tell them that they are losing the internet battle.
Slashdot Mirror
I have been waring my headphones the wrong way! :(
Hmmm.
In five years over clocking geeks will be taking 10MV and pouring liquid nitrogen right into the head while solving PI with 1 billion digits.
Sick!
How about going down to Toys R Us /sarcasm
By a small toy chair.
Rig it wit cupper wire.
And then just zap the litle terrorist.
Broadcast it national TV.
And force all kids to watch it!
Or perhaps someone should sue the judge for
Child abuse ?
Im thinking that judge must be having a serious attention disorder to exploit a 4 year kid just to make headlines.
How sick is that?
At the fertility clinic:
Mom: Damn it!! thats the third democrat. Whatch your aiming!
The Mayas have told us this would happen
Perhaps Nibiru would a suitable project code name
Hum..."that the new specification will greatly increase the 'attack surface' of HTML — providing more avenues by which malicious code can be delivered through the web"
What specification ??
"greatly increase the 'attack surface' of HTML"
Omg. sounds horrible to me :(
Sounds like its gonna turn my browser into remote desktop with a blank password..oh shit!!
> The GUI is just the tip of the iceberg. It's the least important as far as overall functionality, but it's what everyone sees and reacts to.
True. So you have to be a good communicator besides being a good system developer. :) :)
Often you have be good at smooching a litle bit too
Unfortunately, in most cases, being good at your profession is usually not enough when you work with IT
Thats is why you have to walk sometimes even thoug it can be tough.
But you can plan for it and you can learn to become better at navigating through bad projects ( learning by doing
Pitching two developers, teams or even companies against each other maximizes your change of success.
That is:
1. As management, you dont have a clue about what you are doing in the first place (go happy lucky)
2. You dont mind spending the cost two times over
3. To stay in power, You have learned to divide an conquer
But your cost will double
Your employees will start fighting and sabotaging each other
But who gives a $#!7 as long as your happy :)
You need to
1. Understand the business rules.
You need to know what the system / application does before you can begin making changes to the code.
2. Get an overview of the system design / code structure. If there is any (otherwise it is going to be very difficult).
Break down the system into use cases and try to see what part of the code each case covers.
That should give you an idea of the business logic and the class structures (assuming it is not one big bowl of spaghetti).
3. Create a working document with your diagrams and development plans.
Put all your observations on a whiteboard, paper or a napkin as needed. But remember to draw it Visio, Word or OpenOffice.Writer too.
You don't have to do this all at once. It can be done as you move into the code to fix bugs or when making changes.
It will probably take you between 6 to 18 months to get fully acquainted with 30-40K lines of code.
It also depends on how hard business is pushing you. The more pressure on bug fixing and system changes, the less time you will have to learn about the system as a whole.
Even though 30-40K lines isn't that much it is probably more than a one man job.
If it is a business critical system. It is more likely to be a 2-3 headcount.
You should have you own exit strategy ready and get out of there, in case business wont take your challenges seriously.
Anyways i hope they pay you well.
Good luck with it.
In a working environment a nice idiot will always be an 4hole, no matter how nice that person is.
If you cant cut it, just get tf out of there. Nice is a compensation for not trying hard enough.
It is often accompanied by a really good excuse. Leaving the problem to somebody else. Which in the end really isn't so nice.
Because of their lack of skills and inherent laziness, nice people will often smooch their way into middle management positions.
That is the reason why there is so many incompetent idiots in IT management positions.
On the other hand A Rude person that is always right, is just person with a great personality.
In ten years fighter planes will be the size of bumble bees and be equiped with cyanide
Good enough.. Always depends on who you are asking. :)
It also also implies that it could be better, admitting obvious shortcomings.
The supplier will find it good enough when the product meets the requirement specs.
The customer will find it good enough when the product actually supports the business process.
The end user will (almost) never find the product good enough.
Its just a matter of getting the contracts right. Dealing with large government projects, thats as easy as it is impossible
The problem with good enough is that it colides with quality. And bad quality is always expensive in the long run.
The supplier: Just be good at two things. Customer expectation management (do the talk) and Estimating/Developing (do the walk)
The customer: You can't manage what you dont understand. So understand what you are dealing with. Alot of IT managers dont have a clue about IT at all, especially in the government sector.
Looks a lot like the almost 50 year old project Xanadu :D
With cross platform event subscriptions ad libitum?
http://www.xanadu.net/
http://transliterature.org/
http://en.wikipedia.org/wiki/Project_Xanadu
Add both as standards..Why not?
If only MS would add support for SVG and CANVAS. Take a look at this comparison chart: :)
http://www.naxos-software.de/blog/index.php?/archives/45-Interactive-Cross-Browser-Vector-Graphics-on-Top-of-SVG,-VML,-Canvas,-Silverlight-using-Dojos-GFX.html
But MS is rather going for Silverlight as their answer to Flash. Just like that ASP.NET was MS's answer to the internet (it was not working).
As of today Flash does the job while Silverlight might in a couple of years if ever.
Never the less having to rely on third party plugins always sucks.
.
However thanks to initiatives like dojo gfx and others. It is possible to have drawing capabilities with DHTML and pure javascript.
The approach is to wrap the current browsers supported drawing API like SVG, CANVAS or VML. Check the link below. See the Link section in above link.
.
A primitive but practical approach to get (simple) drawing capabilities is making your own drawing library that paints using the good old div tag.
I know that it sounds ridiculous, but Walter Zorn have made a quite useful library, that some use for charts, diagrams, rounded corners etc. See below link.
http://www.walterzorn.com/jsgraphics/jsgraphics_e.htm#performance
.
It would be nice if all the browser vendors would sit down and agree on a very simple drawing API, that would make it possible to draw polygons and primitives and do translations in a cross browser environment.
And then compete on the more advanced plugins for those who need it (the add business who makes annoying banners).
Right now the most experienced and stubborn developers can get around without having to bother with plugins by hacking their own libraries or using open-source alternatives.
Over time libraries like dojo gfx will translate into new standard gfx API's that I guess will help MS to join the rest of the world and become part of the internet.
.
Someone please try to talk some sense into MS next time you meet
Just tell them that they are losing the internet battle.