|
Don't freak out.
I have been working in an Agile w/Scrum for about 2.5 years now, and trust me, the Engineers are the coders/developers/engineer and no one else.
When I got my taste of agile "bootcamp" I saw/heard the same crap.
All is good. 
|
|
|
|
|
Earl Owens wrote: Early on we were told that everyone is a developer
A rose by any other name...still pricks you.
The only thing I've learned from the agile community is how agile the muscles responsible for laughing can be.
Marc
|
|
|
|
|
I am Spartacus!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Earl Owens wrote: So from this we get if everyone is a developer then no one is the developer, and code if written at all can be written by any warm body if we bother to write it at all.
Label doesn't matter to me. What matters to me is what I do during the day and what I get paid to do it.
If they want to throw someone in with little experience I can usually find the time to mentor them which I enjoy doing. And I still get paid to do it.
|
|
|
|
|
Earl Owens wrote: Then my supervisor jumps up and says so anyone can be a coder.
Anyone can be a coder, but not everyone can be a manager. That requires a superior level of stupid.
What we got here is a failure to communicate
|
|
|
|
|
If they're coming out with crap like that they don't know anything about Agile. In other news, your supervisor sounds like an idiot. 
But...if you want to learn what Agile is really about, watching conference sessions from Agile on the Beach[^] (a great conference; can heartily recommend it if you're in range) is a pretty good way to start.
Anna ( @annajayne)
Tech Blog | Visual Lint
"Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
|
|
|
|
|
In the same way as anyone can land a modern passenger plane. There's a couple of people sitting at the front who can probably do it a lot better (and cope a lot better if anything unusual happens) and as a group we therefore decide to let them perform that function.
In civil aviation we call these responsible experts "pilots". In computing we call the responsible experts "developers". In both cases we refer to the cost of not having them as a "plane crash".
|
|
|
|
|
First, realize that Agile is the flavor of the day. And more accurately, is the flavor of the month but could be on its way out soon. Of course people will still jumping on Scrum as it is being replaced by the next great thing.
Second, realize that managers can turn all that is good into all that sucks. The very basis of management in America is based on the premise that you have two classes of people. And they teach the management class that if we can be trusted we should be put into the lower level of their class. If we don't want that, we can't be trusted.
Because of the basic distrust of managers, most places that profess some methodology us some management speak to twist the thing in a heap of dung but remain buzz word compliant. (And Agile is a buzz word today.) There are rumors of some places claiming scrum from daily meetings and ending them by asking about road blocks.
Also, if you ever want some enlightenment, search out the origins of the "waterfall" method of development and see how iterative it really is.
|
|
|
|
|
He must have just watched Ratatouille and made the same analogy.
|
|
|
|
|
Did your agency pay the the firm conducting the Boot Camp? You guys were robbed. Find someone who knows what they're talking about. I applaud your skepticism, sir.
B. Mead
|
|
|
|
|
Why I suddenly need to think about Dilbert?
|
|
|
|
|
I've heard that bus driving ain't too bad!
|
|
|
|
|
Well, if my coding fails miserably I might as well try as an instructor at an Agile bootcamp.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
Snake Oil purveyors are always around; all of these camps and movements and manifestos sometimes smell like an attempt to avoid, or at least postpone, work.
|
|
|
|
|
"Agile" and all the other such paradigms are complete nonsense that are being used to replace simple, common sense so that many people can make money promoting them.
You simply cannot build high-quality systems and applications without quality requirements gathering, quality design, proper scheduling, and technicians who understand that code is as much an art as it is a science.
However, to get around all this we have the latest buzz-word development paradigm in Agile.
I have worked in many shops that consider themselves "Agile" and all of them have boiled down to we simply don't have the time to do the work properly...
Steve Naidamast
Sr. Software Engineer
blackfalconsoftware@outlook.com
|
|
|
|
|
I was the trainer in this particular class and I would like to apologize to Earl for not making the message clearer. In no way was it intended to sound like anyone can do anything. In fact in the class it was specifically stated that the view that everyone can code is a mistake and it doesn't work. That would be a purist/dogma view and would be lunacy. The statement was that everyone needs to step outside their skills and help other team members. Even if it means that BAs test, developers write requirements, or any other combination, "as long as they have the skillset and/or mentoring available to be able to do so". The goal is teamwork, not replacing specialists with generalists.
In addition, calling everyone a "developer" is not intended to reduce the value of that skillset. Instead it's to promote the concept that the entire team is producing the product, not just developers/coders. A tester or BA, etc., is no less valuable than any other team member and everyone is involved in "developing" the product.
I would like to suggest that next time you are in a class and you feel so strongly about something, that perhaps you should ask a question in the class rather than taking to public forums. I would have gladly explained further or had a debate in person. Perhaps then you could have walked away with a better understanding.
Again, I would like to apologize if that message was not properly conveyed.
|
|
|
|
|
Sheesh!
Unit testing done. Solution's automated tests done. Merge to trunk, phew, done. Watching the damn thing build and deploy, is still suspenseful.
You think that I would have gotten over this by now. 
|
|
|
|
|
So, have you picked a name for the baby yet? Is labor almost done?
|
|
|
|
|
You'll have to ask his EXe!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Groan!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
We should come up with a product that allows people to watch automated builds side-by-side with a clothes dryer whilst popping bubble-wrap.
We'll make a Fortune!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
One of the ironies of my long career at my current job (24 years and counting) is the consistency of build times. The product I was building 20 years ago took 45-60 minutes to build and several floppies to archive. Our current products take 45-75 minutes to build, and 1 or 2 DVD's to archive.
Software Zen: delete this;
|
|
|
|
|
Anyone else using Bluemix[^]? I just got free trial access. Later this afternoon going to see if I can cook something up. Got some learning to do![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
I just hope that teenage "Radioactive Boy Scouts" don't get their hands on this: [^].
« I am putting myself to the fullest possible use which is all, I think, that any conscious entity can ever hope to do » HAL (Heuristically programmed ALgorithmic computer) in "2001, A Space Odyssey"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
