|
This is the kind of mentoring I like.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
At times two individuals of about the same level of learning can collaborate and work a problem out (even if its not in the same project). For instance, suppose your trying to implement some code that was published on "CodeProject" and its simply not working. Perhaps your code buddy has run into the same or a similar situation and can provide a clue as to how to implement that code. Or together you can figure out an implementation. It's kind a synergistic relationship. When your working alone and really struggling learning new concepts I suspect a code buddy could be a real asset.
|
|
|
|
|
Hmm. Might be as well to remember that 'two heads are better than one' usually reduces to 'fools never differ'! And what happens when it turns out that one is a far faster learner than the other and is thinking of ways to improve the exchange of information between far space probes while his/her peer is still struggling to get an LED to light up every 20 seconds?
No, it'll all end in tears. You mark my words!
|
|
|
|
|
Language - ASP.NET, C#
Level - Beginner
What I want to accomplish - I want to learn ASP.NET MVC by following these online tutorials
So, in essence, sam technology, different tutorial. I considered Python/Django, and most probably I will do it someday, but I figured I'd try MVC first. 
|
|
|
|
|
It's been one of "those" days... 
Hence:
You should only drink on days that start with a “T”: “Tuesday”, “Thursday, “Thaturday”, “Thunday”, “Today”, and “Tomorrow”
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I'll drink to that!
Mongo: Mongo only pawn... in game of life.
|
|
|
|
|
Hmm, I'm waiting on our resident gin consumer to reword your post.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
|
|
|
|
|
Given that the average human can die of thirst within two days, I've always thought it best not to take chances.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Yes
PooperPig - Coming Soon
|
|
|
|
|
OriginalGriff wrote: You should only drink on days that start with a “T”: “Tuesday”, “Thursday, “Thaturday”, “Thunday”, “Today”, and “Tomorrow”
, unless they overlap ...
|
|
|
|
|
There are only two situations when it's ok to drink:
- When you are with people
- When you are alone
|
|
|
|
|
Apologies for it inevitably being a Leslie, but first I heard of her:
Margaret Hamilton[^], standing next to the source code[^] for the Apollo project code
Edit: updated to the direct link to the graphic (thank you Sascha)
TTFN - Kent
modified 22-Apr-15 19:21pm.
|
|
|
|
|
For those with an aversion to clicking Farcebook links: direct link to the image[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
|
Exceptional lady!
New version: WinHeist Version 2.1.1 new web site.
I know the voices in my head are not real but damn they come up with some good ideas!
|
|
|
|
|
Mike Hankey wrote: Exceptional lady!
Yeah right? Especially considering the year. Must've been challenging for women in those jobs. Here are some more (not sure if it's a Leslie): http://modernnotion.com/human-computers-broke-barriers-women-science/[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
They've definitely had obstacles to overcome.
New version: WinHeist Version 2.1.1 new web site.
I know the voices in my head are not real but damn they come up with some good ideas!
|
|
|
|
|
Quite the legacy! She is even credited with coining the term "Software Engineering", which is a term that is on my business card today... And I had never even heard of her. Fascinating story -- thanks for posting!
|
|
|
|
|
Might need to ask Leslie whether or not he's seen it.
|
|
|
|
|
With the photo being 40 years old, I wouldn't be surprised. However, I'm not as bothered by Leslie as some people.
TTFN - Kent
|
|
|
|
|
Countess Ada Lovelace
Rear Admiral Grace Hopper
Margaret Hamilton
...
I've just read the Wiki page about Ms. Hamilton. It makes me wonder how many other (unsung, unknown) women laid the foundations of our craft?
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
|
|
|
|
|
Wiki Info[^]
If it's not broken, fix it until it is
|
|
|
|
|
Linear feet of code was one of the unofficial metrics for the final project in my HS 2nd year programming class.
RIP Fanfold Paper. ![Rose | [Rose]](https://codeproject.freetls.fastly.net/script/Forums/Images/rose.gif)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
@ all re Margaret Hamilton
I discovered her and her work recently. Amazing woman whose engineering talent we should probably aspire to emulate where possible. Today, there's people trying to figure out how to eliminate interface errors, recovery properly, etc. which she invented and did successfully with 1960's hardware. Anyone interested can read this fascinating paper[^] on their work.
The fun part is that, by Richard Gabriel's classification, this crew stayed on The Right Thing throughout their work. Each problem was noted, understood, and mitigated with new methods/tech. They always tried to find the best approach to everything. They weren't afraid to throw away what wasn't good enough. They eventually developed methods to automate coding, testing and so on albeit with rigid modeling language. Here's what a NASA 2003 report said of the results:
"Her unique ideas included: using priority displays, establishing hard requirements on the engineering of all components and subsystems to eliminate interface errors with the flight software at the systems level, debugging all components and testing before assembly, and simulating every conceivable situation at the systems level before releasing the code. This made it possible to identify potential anomalies and resulted in ultra-reliable code. No software bug was ever found on any manned space flight Apollo mission. She demanded that the flight code be designed to work right the first time."
Great stuff. If I get enough time or funding, I plan to revitalize those efforts in a more usable way. She succeeded in semi-automating design and automating about everything else. There were performance and usability issues. I think, leveraging modern work, the best route to building on her work is to integrate a modeling language for arbitrary systems, a system-grade functional programming language (eg Habit from HASP project), powerful metaprogramming (eg Semantic Designs or Racket), and code generation (eg Esterel SCADE, Perfect Developer). This would let system be specified at a high level with safe, fast, low-level code generated through human directed, verified transformations. Being modular and functional, it could leverage any number of existing or future tools for static analysis, test generation, optimization, and so on.
What do you all think? Does this combination sound worth putting effort into? And clearly I'm talking about new projects rather than legacy applications. 
Nick P
Security Engineer & Researcher
(High Assurance focus)
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
