|
Sander Rossel wrote: How do you want the address formatted?
And the very first question is wrong. defining about the presentation before considering the data.
It only gets worse, "address and house number in separate fields." what? Now you know they are clueless (not all addresses follow this format).
I would stop them there and ask them one simple question: "when are the properly qualified people coming?" If they don;t know ask their boss because all they are doing is wasting your time with zero accomplishment to show for that.
There's not one iota of Agile in that, anybody who calls that so should find a new career asap.
Signature ready for installation. Please Reboot now.
|
|
|
|
|
I'm really not sure what you're going on about...
Sounds like a perfectly valid question (when considering that we only have Dutch addresses in our system and that's not going to change anytime soon).
Perhaps everybody considered the data, but you?
|
|
|
|
|
Sander Rossel wrote: How agile are you?
Put it like this: if my username wasn't "OriginalGriff" it'd probably be "SessileGrog"
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: it'd probably be "SessileGrog"
That's a real Downer.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
In my experience, Agile works when
0. Customer know what s/he wants.
1. Product owner knows what cutsomer wants.
2. DEV knows how to change the Product owner to software.
3. QA tests what DEV delivers,
For any defects all teams Product, DEV and QA collaborate again.
4. Infinite loop 0-3 steps till the final product delivered.
It's really rare to find/build such team, due to skill, willingness, ability to pay more ...
Luckily I able to experience it since the customer is the owner of the Product, it's also participate in DEV and QA cycles.
How agile are you? I only work 30-40hr per week, but much effective with my teams.
In short Agile needs a team collaboration, from customer to product owner, DEV and QA. Otherwise you can't make it to be agile only because you have employees...
Logic will get you from A to B. Imagination will take you everywhere
- Albert Einstein.
|
|
|
|
|
If stakeholders understand how it works and are also agile I am willing to fill gaps o my own.
Of course I probably will miss something anyway, but I don't need to worry that someone will nag.
On the other hand if someone complains after sprint and stories were not specified well enough.
Then the only option is to push back next time.
|
|
|
|
|
Sander Rossel wrote: As an admin I want to see the address of a user on the user overview page.
You missed the zero'th question: Are you actually allowed to see that data under GDPR rules?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
That's not really the programmers job to figure out
|
|
|
|
|
How about a "software engineer"?
You want to be treated like one?
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
I have the strong inclination to split some hairs here but I think it needs to be said. In your two scenarios you are talking about two very distinct things, neither of which have anything to do with AGILE. That happens to be the hair I am splitting. There is a highly important second word that the community has a nasty habit of leaving off when referring to "agile" and that it isn't "agile" it is "agile development". Like I said, a bit of hair splitting but important. Regardless of using agile, waterfall, or whatever; you have to have some basics. You have to have requirements (agile ends up using these to come up with the user stories, or a bunch of different names), waterfall uses this as requirements and etc. through other methodologies but they have to exist first.
Where this comes into your two scenarios is in the first, the questions that are being asked are being asked because the requirements are incomplete and unclear, in the second the requirements are not complete but this fact is being ignored. Agile is supposed to make it easier to develop and handle requirement changes but the community seems to accept, at least in my encounters, that agile is actually designed to allow us to not have all the requirements, and the ones we have not be complete, and we develop without them.
In practical experience what this leads to, at least in my experience, is the first method will ensure that the best application possible comes out in the alpha, beta, or whatever, with the minimal amount of time involved in basic things like layout and page views; the second method is going to result in a large amount of time spent in tedious things like altering a page layout a half an inch so one text box lines up with another, and repetitive views and things like this. I just wrapped a project, as an example, where a page had a registration form and nobody laid out the requirements and by the time we got close to the end, the one view, a simple registration form had been re-done seven or eight times with the irony of the me pulling up the original page and the final page and everybody realizing that the original and the final were exactly identical but we had redone it seven or eight times.
The first reminds me of someone understanding a real development process, be it agile or whatever, and the second being cowboy coding with no regard to thinking things out, wasting effort or repeating work.
|
|
|
|
|
|
It is interesting, I am actually okay either way. I usually tend to do cowboy coding if it is a smaller or a personal project but if it is slightly larger or if it is a work project I think having more details makes for a more successful project.
As software developers, we are used to having things change and shift and not really be locked down, but our customers tend not to be really comfortable with that, especially depending on the industry. I find most customers need a firm set of dates when things will be available, what they will cost and the level of effort things will take. You can't really give them that without having a significant amount of detail.
Quote: Exactly my current situation.
There's two things I can do: bitch about how nothing is clear and we're all wasting effort or trying to figure out what needs to be done and make the best of it.
I'm going for the latter, with the side note that I actually like working that way as talking to people and figuring out specs is a welcome change from programming
This is pretty much my thinking, for the most part, on not having things spelled out. I am pretty able to go with whatever is going on, but I really hate wasting my time and effort even though I get paid either way.
|
|
|
|
|
A "waterfall" project that is "chunked" small enough, becomes a series of "agile" projects ...
It's just a question of being able to prioritize.
(Just looked at a RFP from a muni govt with a "diagram" of their "plan" ... there should be a critical path; but it looks like a super nova ... Pass.)
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
In over 18 years with the same company, I've never worked from a written specification...the closest thing being a UI sketched on scrap paper. When I was new, there may have been more details, but generally my boss would simply describe what a new screen should do...just get it done. Things haven't changed much except now we might discuss what a new application/module should do...the details are left up to me.
The phrase here has always been "We're making this stuff up!". Our business model may be atypical in that our software is provided to clients through annual contracts only. We are expected to know more than the customers/end users about their operations current and future needs.
"Go forth into the source" - Neal Morse
|
|
|
|
|
Yes ... at some point, the "programmer" becomes the domain expert; but not the credit for being so (that's still the "domain" of the BA).
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Agility is proportial to one's level in the current chain of command.
I'm top monkey only at home (and for the time being).
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
If any of you want to play with getting control back over your updates, this thread prompted an idea to create a bat file to possibly do the job. If you have any improvements to the bat, please post them, as I've never mastered all the arcanery behind that process.
@echo off
:while1
sc stop wuauserv
sc config wuauserv start= disabled
timeout 60
goto :while1
Just open a command prompt with administrator privileges and run the bat from there.
|
|
|
|
|
Very cool, especially to implement this without having to write a complicated app, etc. That was basically what I was going to do, but as an app -- didn't even think about writing it as a batch file! There may be some other services that need to be disabled too, but those can be easily added to the bat file!
Thanks!
|
|
|
|
|
My batch file is no longer working - MS seems to have made a super-hidden admin account or something (during a manual update), to take control of the services so they can't be stopped. Is it still working for you?
|
|
|
|
|
David O'Neil wrote: My batch file is no longer working - MS seems to have made a super-hidden admin account or something (during a manual update), to take control of the services so they can't be stopped. Is it still working for you?
I stopped using the batch file as even before the latest update, Windows was still shoving updates down my throat. It must have been sneaking through somehow.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
If you figure out something new, holler. I've played a bit, and successfully taken ownership of the wuaueng.dll and some others, but still get '5' error with the batch file saying access denied. Maybe have to take ownership of svchost? Don't know - hesitant to play with that one.
Happy New Year!
|
|
|
|
|
so you replace 1 program that runs continuously in the background with another.
fascinating.
just curious, (I'm not on 10), what about stopping it and renaming the service .exe file?
at least if you want it can rename it back. (Could have a couple of .bats, at least they need only run once.
Signature ready for installation. Please Reboot now.
|
|
|
|
|
Lopatir wrote: so you replace 1 program that runs continuously in the background with another. But one of those causes considerable grief when your machine restarts without your permission. And technically, it is not a replace! They both keep running. But such is life in this case. Checked, and the command prompt is stuck at 0% usage if that is any consolation.
Lopatir wrote: just curious, (I'm not on 10), what about stopping it and renaming the service .exe file? Might be possible, but there are a couple other background processes that Windows runs that might trigger the file to be reimplemented. And I'm not knowledgeable about them.
edit: maybe - reddit thread showing which service dlls to rename, but the wuaueng.dll is not in the newest version of Win10.
modified 20-May-18 13:08pm.
|
|
|
|
|
There is no windows update on Linux!
|
|
|
|
|
Why would I update something I don't use?
|
|
|
|