|
This is great! I'm fairly well trained in Agile and I could find my way around JIRA. Let them find their way around my work. Thanks for a great tactical suggestion... I am working my way up the chain today though, asking where they got that interchangeability idea. At 2 is the meeting with the top Agile person and I'll ask her.
As for me resigning, they broke up the band already. Two of the critical people are now on the Run team and both want to quit. I'm the only developer left on the Build team... as we do the digital transformation dance to AWS ... Lambda. You tell me how that's going to happen. I told them when they proposed it that it was an unmaintainable system. AWS says not to try to convert big applications to Lambda. Even our Cloud top executive said a Lambda shouldn't be over 70 lines long. Ours includes over 135 .cs files. I'm stressed out enough that I can't sleep.
modified 10-Jun-21 6:05am.
|
|
|
|
|
Michael Breeden wrote: I'm stressed out enough that I can't sleep.
This is a sign you need to switch over to Team Run as well, after doing one last project on Team Build: An application that automatically locks your computer at 5PM on workdays and won't allow an unlock until 8AM the next day.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing 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
|
|
|
|
|
When they want a generalist and specialist in one package 
|
|
|
|
|
So where did that idea of identical skills on the team come from?
higher in the hierarchy a thing must have changed. maybe as far as two years ago.
although it will be great for all of you to make that fast knowledge transfer, the situation smells like someone has been appointed to cut the workforce or someone (presumably new in the management) wants to show off by cutting costs.
if you stay and they cut somebody else you'll get overloaded with work. all i say is based on my personal experience, i may be 100% wrong.
my tendency is going to places that are more relaxed for work, even if they pay less. that is, if one can afford such a job.
|
|
|
|
|
It is a goal state that everyone can do any ticket. Avoiding silos is a Good Thing(tm). It's also good for your career if it lets you learn new things. That said, it is a management failure to think this will happen on day one.
If management wants this to work, they have to acknowledge that software development is an impossibly broad field to master (like, say, medicine). They then must dismantle all the specialist cross-functional teams and create teams based on skill set (a C++ team, a db team, etc). They also have to allocate time for cross-training and documenting. Betcha they didn't do that.
They probably expected agile to work by magic. Just by saying it's name, they could summon agile. I wish it worked that way but it doesn't.
|
|
|
|
|
I don't see how specialized teams could help any - C++, Db, etc.
I don't think they consider that SW development might be difficult.
I document. No one else does. ... Ya know, all the other teams are far bigger. Maybe that helps them.
I think there will be panic before magic.
|
|
|
|
|
I have run into the same Agile mentality at my last two companies. It seems that developer interchangeability is "the elimination of siloed skills" that is the Agile buzzword of the day. Both companies were experiencing developer turnover and reductions.
|
|
|
|
|
Fascinating. Now that sorta makes sense with what is going on. I wonder if they notice they aren't producing any software?
Were those companies choosing to reduce the number of developers or were they just leaving?
I think the question will be "are you still going to produce software"? And then "who is going to produce it"?
... So, "we need interchangeability of skills". "That sounds like a great idea, I could use some help". "How are we going to do get people up to speed with the tools we use"? Ya know, it really fits with the amazing loss of talent we've had. 2/3 of the team is gone. There is no one to maintain the systems I built and always maintained. Well, ... the pressure is on. Yesterday, my former manager said that the project timeline would need to be doubled. The new "HR manager" said that I and the two new guys (MS ecology, not Open Source) would need to step up and start that project moving. I mentioned that I've been working 11+ hour days. Better still, I told them from the start that that technology was unmaintainable by mortals. I wonder how long it will take.
|
|
|
|
|
First company was restructuring and attrition. Second company was a mixture of constant firings, attrition and dictatorship Agile driving good developers away. Three developers left my first month and the rate reduced a bit, but was still constant. I was a contractor let go after 9 months.
|
|
|
|
|
My first IT job was as a Trainee Programmer, working on an ICL 1901, with 16K, (words), of memory and no hard disk. All data processing was done via mag tape.
Programs (COBOL & Plan Assembler) were hand-written on coding sheets and punched on to paper tape, by the punch & verify team. Your program was compiled overnight, by the operators, and in the morning you arrived in fear of the missing full-stop, that generated dozens, (sometimes hundreds) of compile errors. There was no Development, Test or UAT systems. Just Production.
These days, I tweak a few lines of code; build/compile; unit test; repeat. Sometimes dozens of times for the same routine - because I can't be @rsed to think through how the whole program should work. And then I have the 'safety nets' of Code Review, QA and UAT.
Who'd have thought 40 years ago, I'd be sitting here today with my own computer (with a screen!) gradually honing my code until I manage to get something close to working. Back then I'd have been happy to have a sharp pencil.
In those days, you had to be disciplined and you had to get everything right. The young people of today...
The Four Yorkshiremen Sketch - YouTube[^]
|
|
|
|
|
I don't believe you 
|
|
|
|
|
ICL 1904 under George III for me (university computer). Punched cards that you had to punch yourself, and operators who dropped them just for the heck of it.
First actual job was a Prime 400 at 0.5 MIPS, 8 MB of memory, and 160 MB HDD. This ran with 32 concurrent users logged in and working. Gawd knows how, that wouldn't run a digital watch these days ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ah, Harvard architecture. I like that. Many registers in the processor, memory may have the weirdest word formats. Sounds like fun.
And you would not believe what you get when some former mainframe guys decide to design a microprocessor that way, a hybrid between Harvard and Princeton (aka. von Neumann) architectures with the somewhat limiting word size of 8 bits.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I started as an operator on a LEO III - 16k words of memory, card and paper tape input (and output), and magnetic tape for speed. One of the best features of the LEO was the radix register which allowed it to do calculations in LSD. Learned machine code programming in my spare time (in between drinking and chasing girls).
|
|
|
|
|
Richard MacCutchan wrote: the radix register which allowed it to do calculations in LSD
Did you mean BCD, or was this computer designed by Timothy Leary? 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
No I mean our old currency: £sd - pounds, shillings - of which there were 20 in a pound, and pence - of which there were 12 in a shilling.
So £2/13/11 + £5/8/4 = £8/2/3.
|
|
|
|
|
I know what UK currency was like before decimalisation, but I've never seen it called LSD. Thanks for clearing that up for me.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
It's from the Latin: Libra, solidi, denarii.
|
|
|
|
|
What prompted this post, was realizing how incredibly easy Software Development is now days. I was being incredible lazy: changing a few lines of code; testing; and then back round to do the next few lines. Which I suspect is the norm these days.
Imagine having to write an entire program, (in COBOL or Assembly language), by hand. And, if it compiled, the next step was to put it into production! If it didn't work our options were either put a, machine code, patch into memory and rerun or splice the mod into the paper tape, recompile and run. How scary is that? 
|
|
|
|
|
Dude, I thought I was old.
When I came into the digital world from analog instrumentation there were already Rk05 2.5mb disk pack style drives and the glorious vi editor in play.
That must have just sucked to see the next morning coming.
|
|
|
|
|
Not really, no - we saw it as a natural progression, and tools to make life easier.
Mostly because we all knew the old way worked-but-was-sh*t and the new way almost-worked-but-was-way-easier.
Except vi: nobody could ever remember how to get out of that.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I started with paper tape via a teletype machine on an acoustic coupler to a remote IBM way off in the big city (Manchester). Later I worked with Pr1me computers at the polytechnic - they had greenscreens, advanced technology. I still remember getting 50+ error messages from one missing full stop - none of which mentioned the aforesaid full stop. Eventually got a real job working on ICL equipment (2960s I think) but back to punch cards. We also wrote the code (FORTRAN IV) on coding sheets which were processed by "punch girls" to create overnight compilation runs, debugging involved changing out one or more cards, occasionally punched personally (when the unions weren't being awkward) and eventually straight into production - no, test system. Lots of finger crossing! A year or so later we got green screens but the head of the department hated them and tried to make us stick to punch cards for another year until they took the machines away. He also hated Fortran-77 on the VAX machines we used for the real-time system. He couldn't cope with names longer than six characters in mixed case!
I won't mention the compulsory flowchart requirements... oops, just did.
Aah, the good ol' days!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Quote: I won't mention the compulsory flowchart requirements... oops, just did.
I go back to the 60's. I remember a human factors course I took in the mid 70's. The professor said they had done an experiment to test flow charters versus non flow charters. Seems the flow charters got their program running with fewer compiles but the non flow charters made friends with the mainframe operators and got more runs. Time came out about the same.
I still have my plastic template around here somewhere. Same drawer with my slide rule
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
I still have my flowchart template somewhere. Going to spend the next 5 hours trying to find, it!!
|
|
|
|
|
I found that the surest way to get more runs was to occasionally show up in the machine room with 12 dozen homemade, still warm chocolate chip cookies (one advantage of living fairly close to work). I could've gotten away with murder for at least a couple of weeks after that.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
