|
Elm met by moonlight?
I am not a number. I am a ... no, wait!
|
|
|
|
|
Looks like a Lincoln Town Car. If that is the case, there should be plenty of room under the hood to plant a tree. I'd guess that the radiator and attached hoses and belts were severed, but if that has a cast iron block and heads, it should last a good 15 to 20 minutes without cooling.
|
|
|
|
|
"This neighbourhood is so green. Lots of trees. I think I should move in here. [takes a drag of whatever]"
"You'd have to be a floating database guru clad in a white toga and ghandi level of sereneness to fix this goddamn clusterfuck.", BruceN[ ^]
|
|
|
|
|
His English homework this week was to answer the following questions about the last book he had read.
"Who do you know that would like to read it and why?"
"Who do you know who wouldn't like to read it and why?"
He said to me this is really hard Daddy, it's easy to say who would like it because all my friends like Diary of the Wimpy Kid, but I don't know anyone who wouldn't want to read it. I agreed it was hard and somewhat a negative way of thinking about one of your favourite books but I told him to go away and have a think about it and I'm sure you'll come back with something. Ten minutes later he came back and proudly showed me his homework book where he had wrote
"Freddie Kruegar would not like to read Diary of the Wimpy Kid because every time he tried to turn the page his razor hands will shred it to pieces"
That's my boy, no need for a DNA test there. Can't wait till see how his Teacher marks it.
|
|
|
|
|
|
Keep us updated... I'm quite curious too...
Think, it could also depends on the age of the teacher 
Jeeeeez... I'm old 
(yes|no|maybe)*
"Fortunately, we don't need details - because we can't solve it for you." - OriginalGriff
|
|
|
|
|
Be prepared to meet his teacher and a social worker 
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Vote up or Mark as Answered, if this information helped you.
Kind Regards - Kunal Chowdhury, Windows Platform Development MVP
|
|
|
|
|
PompeyThree wrote: "Who do you know that would like to read it and why?"
"Who do you know who wouldn't like to read it and why?"
Shouldn't that be "Whom" ?
|
|
|
|
|
The first sentence doesn't use a relative personal pronoun, either, so I vote we take up a petition to sack this moron who's pretending to be an English teacher.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
C-P-User-3 wrote: Shouldn't that be "Whom" ?
Nope. Sorry. Oxford Dictionaries has declared the use of 'whom' in this context unnecessarily exaggerated formality (as close as they will ever come to saying 'incorrect'!) The simple interrogative is properly treated differently to the relative pronoun. It is one of many examples where the rules (which you will remember were arbitrarily imposed by an intellectual elite anyway) have never truly reflected actual use.
I am not a number. I am a ... no, wait!
|
|
|
|
|
Well Duh. Thank you. My education continues. I thought for sure it was whom.
|
|
|
|
|
I am writing a paper for a writing class that I am currently taking, and I plan on writing on the subculture that programmers are a part of. So basically I have 2 questions that I need answered, and appreciate everyone's responses.
Question 1.) Why do you program, and what attracted you to programming in the first place?
Question 2.) Do you see any problems or future problems that could arise within the programmer subculture?
Thank you all in advance for the help.
|
|
|
|
|
1: bacon
2: not enough bacon
|
|
|
|
|
Quote: 1: bacon
And coffee. Don't forget the coffee! 
Get me coffee and no one gets hurt!
|
|
|
|
|
Pizza, bacon pizza!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Quote: Pizza, bacon pizza!
And coffee, Coffee, COFFEE!
Get me coffee and no one gets hurt!
|
|
|
|
|
Others did it and it seemed cool and smart to do so I did.
Subculture: Girls won't be attracted to that, play lead guitar or better yet, drums.
|
|
|
|
|
My answers:
Question 1.) Why do you program, and what attracted you to programming in the first place?
The chicks! Nah! I got stuck with it, I'm a hardware guy who basically got stuck with VB6 thing that didn't work.
Question 2.) Do you see any problems or future problems that could arise within the programmer subculture?
The issues, well the lack of bacon & ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) and the limits of processor technology.
|
|
|
|
|
- Mid-life crisis!
- Mid-life crisis!
I am not a number. I am a ... no, wait!
|
|
|
|
|
From someone at the tail end of a programming career.
- The endless challenge of keeping up with software tools. The challenge of deciphering the specs from business. There was no attraction, it was a tool used to help sell stuff!
- There is a subculture? Where... It is difficult to identify problems from the inside, oh wait, yeah bacon, a definite lack of bacon!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Answer 1: I program now because it's my career. I've been a professional programmer for 35 years, I'm pretty good at it, and it supports me and my family. I grew up watching the Gemini and Apollo launches. While I liked the idea of being an astronaut, the thing that really fascinated me was the idea that computers controlled the whole thing. I wanted to learn how to do that. I took a programming seminar in high school, plus my step-dad built a home-brew computer we learned how to program together. I majored in computer engineering in college, and figured out that I was much better at software than hardware. I've spent most of my career on data acquisition and process control applications.
Answer 2: I think one of the more fundamental problems in the culture arises from the communication gap between ourselves and the organizations that employ us. We don't understand them and their requirements. They don't understand the implications of some of their decisions, especially when they change their minds mid-stream. Like I said, I've been at this for 35 years. This poor communication is just as much of a problem now as it was when I started. In some respects the problem's gotten worse, due to unmet promises from heavily-promoted methodologies that are only partially or incorrectly applied.
When I started programming, we were finally leaving the era of programmers as high priests, inaugurated into the mainframe's mysteries, when users made offerings to receive the priest's blessing. We were entering a period when becoming a programmer was a practical choice for a lot more people than an isolated few. Now, anyone can and does learn how to program. Significant numbers of people are self-taught and earn some sort of income through programming. This has created an organizational mind-set that programming ability is a commodity. Fifty off-shore programmers at $10/hour are just as good as ten local programmers at $50/hour. The problem with this idea is that it does not take into account the fitness of those teams to their tasks. That team of fifty might work perfectly well for a line of business, data entry application, where best practices are well-known and easily followed. Software that requires extensive domain knowledge and background experience could be more appropriately handled by the local team. The methodology gurus have unfortunately convinced the powers-that-be that the fifty programmers are just as good as the ten, if only you apply XYZ process to managing the project.
Software Zen: delete this;
|
|
|
|
|
Gary R. Wheeler wrote: Software that requires extensive domain knowledge and background experience could be more appropriately handled by the local team.
That makes more sense than any other argument I can think of.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Answer 1: I've been doing this almost as long as Gary -- my college class was among the first (at that college) to graduate with an actual Computer Science degree. The short answer to why? I'm a geek at heart, I like building things, and IT looked good. Also, I had no other idea what to do with my life. Looking back over my career? I made a good choice. Yeah, I've had some bad assignments, but overall, life has been good and I've got more years to go. I like what I do.
Answer 2: Problems are legion. As Gary pointed out, bad communication is rampant. Some of that is our fault, not taking the time to understand the business or to look at things from our customer/client/business partner's POV. As much is on the other side, with folks who don't understand what they want, provide poor requirements, and/or think that computers are a magic bullet or (alternately) that we IT folks are disciples of the Devil.
Pointy Haired Boss type managers make it worse. Too many don't understand what their employees do, lack people management skills, and lack business management skills. [In contrast my current supervisor is a pleasure to work with.]
The solution to the above is often patience. When everyone treats everyone else as someone to learn from and focuses on getting the job done right rather than right now, things go better.
Following on with what Gary said, I see outsourcing as the #2 problem. Note that I'm speaking from a USA perspective with respect to onshore and offshore.
Part of this is communication, due to cultural and language differences. Things often don't get translated properly and the onshore company gets products that do not fit the needs. This often causes unpaid OT for the onshore IT folks, fixing things while not affecting the manager's bottom line. Or it causes business delays as things have to be redone to get them right. Plus timezone differences -- having your development team 10.5 hours ahead of you can easily cause a day delay on any given topic. As a manager for offshore teams, I typically conduct 7AM EST standups to give my teams feedback at the end of their day to set them up for their next day. This works, but requires diligent effort and (yes!) effective communication.
Along with that are personnel problems. IT is big business and at least some of the offshore workers are NOT fit for the job, they get hired 'cuz they have a pulse to fulfill a contract. It's harder to vet as the onshore folks are not directly interviewing many of the offshore people. IT is treated as a commodity, which foolish. In addition to technical skill set, a good IT person brings personal ability, general experience, and exact domain knowledge to the table. Plus a willingness to learn. THAT is critical for everyone.
The same managers who do blindly offshore work also believe that 9 committed women can make 1 baby in 1 month ...
Not that outsourcing doesn't work, but the offshore center requires a manager who can communicate effectively with his/her counterparts in the USA and BA and P/A with the right experience and domain knowledge. Both sides require excellent communications skills and patience. It's just not that easy.
Problem #3? Prima donna IT people. Too many people focus on what they are doing and don't see the bigger picture. They don't truly see the business need, nor understand that our job is generally to fill someone else's business or personal needs.
Which loops back to Point #1 ... communication ...
|
|
|
|
|
Answer 1: Repaired computers on A6 aircraft while in the Navy (Viet Nam war). when I got out in '73, I got married and went back to College (B.S. Management). I needed a job and had "computers" in my resume. Got sucked-in from there. Took a 3 hour course in Basic programming, and started writing programs for my boss at the time. I was attending Law school at night by then.(graduated with JD in '80). Sold my first "commercial" program in '79. It was written in GW-Basic and a Radio Shack salesman (remember the TRS-80?) talked me into it. Went to work at a law firm for the next 2 years and 2 things happened simultaneously. I kept raising the price of the software but the RS salesman kept selling it. I also became increasingly disenchanted with the legal profession as a career. (Not enough BACON! ). The rest is, as they say history.
Answer 2: Currently, I am consulting, because the small developer is being squeezed out of the business. I still have a few clients (less than 10) across the southeastern U.S.
Problem 1 with the future caused this. The deliberate and wanton changing of operating systems and programming tools by Microsoft and others, to increase their bottom line and shareholder distributions by forcing customers to purchase new hardware and software. (Think Windows10 vs. XP, software as a service, the Cloud  . There is not enough time to redevelop packages written in one flavor of VS, before a new flavor of the month comes out. If the big corporations are struggling with this and pushing back (complaining) what do you think is happening to the small business like mine? Much less the small business that are my customers. The pace of change is not being driven by technical innovation, it is being driven by Greed.
Problem 2 Data security, hackers, crooks. If the big companies (Microsoft, et al.) put as much effort into making the o/s and development tools secure, as they do in marketing efforts (trying to keep up with the cool kids - think Apple), then they could put out products and let them stand on their own.
Problem 3 Vertical integration (the Apple model). When everything is proprietary, the talent pool and innovation that got the industry here today will dry up. thankfully I will be taking a dirt nap by then...
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
