It looks like you're new here. If you want to get involved, click one of these buttons!
Subscribe to our Patreon, and get image uploads with no ads on the site!
Base theme by DesignModo & ported to Powered by Vanilla by Chris Ireland, modified by the "theFB" team.
Comments
Many guitars have a re-sale value. Some you'll never want to sell.
Stockist of: Earvana & Graphtech nuts, Faber Tonepros & Gotoh hardware, Fatcat bridges. Highwood Saddles.
Pickups from BKP, Oil City & Monty's pickups.
Expert guitar repairs and upgrades - fretwork our speciality! www.felineguitars.com. Facebook too!
Remember, it's easier to criticise than create!
I think I've heard that one from at least twenty ex-coworkers and at least 3 current co-workers.
Do you know what they all had in common? They didn't have half an idea about what scrum is meant for (between them) ... having never been trained in it, worked with Agile consultants -- so basically it's the same bullshit as any other that gets foisted on grumbly developers by managers trying to get them to do something without whining.
As for coding standards - that's easy - the tech lead enforces a house style with a tidy program and commit hooks on your version control system. Then you can save yourself the bother of getting exasperated or grumbling.
But Agile (and as part of that Scrum) is document-light - the reason being if you talk to people rather than email them documentation to read, you tend to get more stuff done. People don't read the documentation anyway, or if they do they get litigious and didactic about it.
That said UML diagrams can save a lot of time, if used sensibly.
I had a job in 2000 Comparing DSDM, Rational Unified Process, XP and ePrince - they were all shit, better than Waterfall which is basically the hierarchy of a company turned into a timeline : the clients shit on the salesman, the salesmen shit on the the managers, the managers shit on the business analysts, the business analysts shit on the software architects who shit on the lead tech/analysts who shit on the developers who shit on the ops people who shit on support who shit on the client.. it's only been around since the 70s and it never works - but at least everyone gets someone to shit on.
These days I prefer to work in ISO9000, ITIL environments using Scrum or Agile properly, ideally wrapped in 6 Sigma process and I don't trust developers who think they're too cool for that - work devops at a bank and you can't trust those people - they make very expensive mistakes and are usually too egotistical to own up to it even when presented with logs, strace, their commit history and test coverage.
One thing that bugs me at present - when the requirements baseline isn't maintained - how the blue blazes is a support team supposed to make sense of the original user stories and backlog, that has morphed umpteen time through sprints. Who the hell can now establish what the system is supposed to do ? </rant>
Also ... the rest of an organisation will likely be waterfall - Agile does need some sort of waterfall wrapper or it ends weeks ahead (or behind) the rest of a programme (or worse - other programmes)
Feedback
Here's a snippet from a mass of old ASP code that I was asked to maintain..
I steadfastly refused to do so! :-S
While not tra.atEndOfStream
x=tra.readline
'if instr(x,k)>0 then
aa(i)=dd(x)
bb=split(aa(i),",")
'Response.write("<br>"&bb(17))
bbs=split(ucase(bb(17))," ")
if bb(17)<>"" then
got=false
for j=1 to co-1
if bbs(0)=cco(j) then
got=true
at=j
j=co-1
end if
next
if not got then
cco(co)=bbs(0)
at=co
co=co+1
end if
got=false
for j=1 to cccnt-1
if bb(8)=cc(j) then got=true
next
if not got then
cc(cccnt)=bb(8)
ccn(cccnt)=right(bb(9),len(bb(9))-10)
ccat(cccnt)=at
cccnt=cccnt+1
end if
end if
i=i+1
'end if
wend
Seriously: If you value it, take/fetch it yourself
Apart from protecting their jobs, I never understand why people feel the need to use magic-numbers and variable names that you cannot search for. My last phone call to a professor who's code I was asked to look at included the question ' what does the number 748 mean in line 463 of your code?' The answer was ' Umm I can't remember... I think it came out of a spreadsheet'
Sometimes I really do despair
One ecommerce system running Agile/Scrum - alignment of dates/deliverables/interfaces becomes an issue.
Feedback
Seriously: If you value it, take/fetch it yourself