|
Yep. Being able to spot the fine details is one of the hallmarks of a good developer...and that doesn't appear to be one of his gifts...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
To be fair, it's not obvious that you would find that forum as a sub-entry of "Application Lifecycle".
|
|
|
|
|
manchanx wrote: To be fair Is the job market "fair;" can Fresher expect to sit at home with employers visiting them to offer lucrative jobs ?
If Fresher doesn't do their own research, paying attention to details, and produce a good resume, and network with contacts, and make sure the resume gets in the hands of people who might offer them a job, is that "unfair" to him/her ?
In my own experience as a programmer (when I worked for "other people") while serendipity did, indeed, bring some fortunate opportunities my way, I worked very hard to put myself "in that way," and keep my eyes on it, and seize the opportunities that "just happened."
Aristotle: “We are what we repeatedly do. Excellence ("Arete"), then, is not an act, but a habit.”
«I'm asked why doesn't C# implement feature X all the time. The answer's always the same: because no one ever designed, specified, implemented, tested, documented, shipped that feature. All six of those things are necessary to make a feature happen. They all cost huge amounts of time, effort and money.» Eric Lippert, Microsoft, 2009
|
|
|
|
|
You're right, the job market isn't fair. But I think a Fresher should be granted to still having to learn how to deal with that.
|
|
|
|
|
I agree with you in the sense that I think everyone deserves a friendly welcome to CodeProject, and gentle, rather than harsh, feedback to guide them ... if they then, over time, prove they don't give a hamster's ass about this community and its guidelines, well ... even then, while refusing to tolerate their behavior, there's no need to make fun of, or attack their character.
cheers, Bill
«I'm asked why doesn't C# implement feature X all the time. The answer's always the same: because no one ever designed, specified, implemented, tested, documented, shipped that feature. All six of those things are necessary to make a feature happen. They all cost huge amounts of time, effort and money.» Eric Lippert, Microsoft, 2009
|
|
|
|
|
cheers!
- Sebastian
|
|
|
|
|
Thank You @BillWoodruff
Don't watch the clock;
Do what it does.
Keep going.....
|
|
|
|
|
Step 0: Make sure you're a software development fresher.
Step 1: I never made it as far as binary, so I have to stop there.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Thanks @Mark_Wallace...
Don't watch the clock;
Do what it does.
Keep going.....
|
|
|
|
|
Do you have any friends/family that already work as developers who could give you an in?
That's by far the fastest way to get started. Apart from that, spend lots of time on reading articles on CodeProject, watching videos on Pluralsight, applying for every job going (not just in IT, better to be employed in any respect than not be employed) and just be relentless in trying to get that first programming job.
|
|
|
|
|
Thanks @JMK-NI for your valuable suggestion..
Actually I did and doing all the things you said(including reading articles on CodeProject) and didn't know the Pluralsight but I visit that site its good and CodeSchool also ...
thanks for the Site...
Don't watch the clock;
Do what it does.
Keep going.....
|
|
|
|
|
Well, scientists announced they can now store data in DNA. One has to wonder if that's how life here got started - "Coded" DNA left on the surface of the petri dish that we call "Earth".
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 17-Feb-15 10:30am.
|
|
|
|
|
Well... if we follow the timeline of bits available backwards from 64 to 32 to 16 to 8... so on, so forth... it was truly binary programming then?
Well... that makes sense... 1 and 0... in a phallic sort of way...
|
|
|
|
|
DNA uses triplets of four possible nucleotides (Adenosine, Cytosine, Guanine, and Thymine) to encode 21 different amino acids. This implies a 6-bit system with some redundancy.
Perhaps DEC's early PDP machines (12-bit PDP-5 & -8, 18-bit PDP-1, 36-bit PDP-7 & -10) were on to something!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I think it may be a trinary (+0-) system with significant null states.
The difficult may take time, the impossible a little longer.
|
|
|
|
|
A DNA codon consists of 3 base-4 digits (each digit may be one of A, C, G, or T), giving a total of 4^3 or 64 possible values. I fail to see how you could represent 64 states in trinary without some "forbidden" values.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
You are correct. That's what I get for trying to do complex math in the wee hours of the morning.
Just as an aside, what would our computer math be like if the early computer developers had used three states for a bit instead of two?
The difficult may take time, the impossible a little longer.
|
|
|
|
|
It depends on which ternary notation you mean.
If we used "standard" ternary notation (0, 1, 2), the increased complexity of the circuitry is very likely to make it uneconomical compared with binary notation.
Calculation using balanced ternary (-1, 0, 1) has some advantages, but I question whether the increased complexity of the circuitry would make it more viable than binary. I note that only two models of ternary-based computers were built, both in the Soviet Union. Neither was a wild success.
http://en.wikipedia.org/wiki/Setun[^]
http://www.computer-museum.ru/english/setun.htm[^]
If, however, we were to use ternary logic as representing "no", "maybe", and "yes" (i.e. one value implies that the datum is uncertain), we might have something new. I don't know of attempts to program "fuzzy logic" in ternary, but would be interested in any examples...
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
|
Then it's only a matter of time before the NSA puts spyware into our DNA!!
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: The difficult we do right away... ...the impossible takes slightly longer.
Miracles by appointment only?
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Richard Andrew x64 wrote: Then it's only a matter of time before the NSA puts spyware into our DNA!!
The whackjobs are probably thinking that's the whole point of GM food.
|
|
|
|
|
Shame they didn't debug the code first
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
John Simmons / outlaw programmer wrote: scientists announced they can now store data in DNA.
This is actually, very interesting to me. I will fight the urge to post back funny/not funny comments.
This also sounds a bit scary.
|
|
|
|
|
I think it may be a trinary (+0-) system with significant null states.
The difficult may take time, the impossible a little longer.
|
|
|
|