|
Kornfeld Eliyahu Peter wrote: Tips and tricks?
Don't do it. 
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
Can you elaborate on that my friend Giskard?
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
Slight;y joking - takes a complete mind set shift ot get your head around the differences. At least it did for a thicko like me.
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
Privately I'm using git, but at work we had TFS, but now they are talking about to move on... I just try to figure out how bad it will be...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
don't panic.
commit and push to your main repository often (in a branch on github or bitbucket for example)
find a proper workflow that work for you (there seems to be many different ways to do the same thing).
rebase is evil.
merge from main branches to your local branch often (reduce the conflit resolving pains)
use pull-requests.
I'd rather be phishing!
|
|
|
|
|
Use a decent app (I use SmartGit – Git Client and love it.)
As others have said elsewhere, learn the difference between a server-based repo (TFS) and a distributed repo (Git). Understanding that will save you a lot of confusion.
Learn/practice branching, merging and stashing with Git with a dummy project.
|
|
|
|
|
I didn't ask what Git is or how to use, but asked about moving an existing project (of enterprise size) to git...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: but asked about moving an existing project
Ah. My bad. Monday morning and all that.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: about moving an existing project (of enterprise size) to git...
Sounds like the beginning of a wonderfully useful article - let us know when you post it! 
I'm pretty sure I would not like to live in a world in which I would never be offended.
I am absolutely certain I don't want to live in a world in which you would never be offended.
Freedom doesn't mean the absence of things you don't like.
Dave
|
|
|
|
|
A chaperone wearing a shredded corset? (6)
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Escort - anagram of corset
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Yep. All yours for tomorrow.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
It is yours today.
... such stuff as dreams are made on
|
|
|
|
|
I'm on it. Public hol here today, so my day is a bit confuzzled.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
You won on Friday.
@Peter-in-2780
|
|
|
|
|
Underscores, not hyphens!
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I see. How about if there is space in the name?
|
|
|
|
|
It's not the Username you use in an "atsign-code", it's the MemberName.
Your's is the same, mine is the same - because that was UserName we signed up with. But not everybody did: some sign up with the default "Member nnnnnn" then decide they want to stay, or they decide they want a change: Has Anyone Seen Mike Hunt - Professional Profile[^] his MemberName is "Micheal-Martin" because that is what he signed up with (probably to try and get his account back - he holds the CP record for "most times banned in a 24 hour period")
So go to the home page for the member, and the "atsign code" is in the top left of the page.
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Neither weird nor wonderful so I'll dump it here for your amusement.
One of our devs mentioned he had some really nasty requirements WPF on SQL server...
Open a dialog and gather filtered data from 4 tables and display in a pivoted grid.
Show YTD, projected to the end of year and 3 additional projection years.
Show reference values from one of the source tables
Accept input from the user for each projected period
Default the user input to the reference values
Do not allow the user to accept the default values - insure the user inputs fresh information. Zero is a valid input value.
The last 2 lines got rejected - emphatically!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: Default the user input to the reference values
Do not allow the user to accept the default values - insure the user inputs fresh information. Zero is a valid input value.
Hint text (like a search box)?
or if you like fancy graphics hint bubbles?
or even better. have an animated puppy or paper clip slide down the screen and suggest what to type. Who wouldn't love that?
Not saying the show-default-but-force-user-to-retype idea is ever good, (monkey see ...)
just sayin' there are ways to do it.
(and today I'm in a "that's what you want? OK, that's what you'll get" mood.)
|
|
|
|
|
My usual mode is "Be careful what you wish for. You might get it.". It's one of the few things that can actually convince people to stop and think. Some people. Sometimes.
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.
|
|
|
|
|
Oh it can be done alright, the dev had already mapped out and possibly even built it, I heard when some additional bloody silly requirement was proposed that was going to impact this.
How do you teach a junior dev to say no to a users request?
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: How do you teach a junior dev to say no to a users request?
Stand between them?
... such stuff as dreams are made on
|
|
|
|
|
Mycroft Holmes wrote: How do you teach a junior dev to say no to a users request?
Why does he need to? Can every Bob and Todd call him and tell him what to do?
Should there not be a limited number of people who are responsible for making any requests on the customer's side and also a limited number of (senior) people who take those requests and react to them? Have the juniors sit on your lap while doing that, and let them give their opinions after the customer has hung up, but don't leave them alone with the problem.
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.
|
|
|
|
|
CodeWraith wrote: Should there not be a limited number of people who are responsible for making any requests
There is only one!
Problem is the dev is not really a junior but has not the skill of telling the user she is an idjit.
Never underestimate the power of human stupidity
RAH
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
