The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
as I said only a Frenchman could say this was a victory, 1/ the French invaded Belgium - did they keep any ground NO so that's not a victory 2/ the Allied force suffered fewer casualties so no victory if you use the stupid body count method 3/ the allied force withdrew without hindrance by the French (not usually a sign of defeat)
so best you could say would be stalemate, it would only be a victory if the Allied force was French (it did have a sizable French component)
From I have read it is claimed as a victory on the assumption that the Allied force was there to topple the revolutionary government, yet I understood that the Allied force was raised to resist the French invasion of Belgium, something it did, so you could say that it was the victor, the fact they carried on into France was not an original directive
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
but it really has little support in historical facts.... Finally, let me recommend a serious place for people interested in history
Not sure how the first ties to the second.
I went to the site and poked a couple of the latest questions and the specific sub-section and I wasn't really impressed with either.
A historian of course should be aware that, since history is human based, there will always be outliers. One can answer a question that requires a comparison by citing examples that could be outliers. Not unless one can demonstrate that they are not outliers.
To be specific to answer the question about whether france surrenders or not one must compare different countries and do so for different time periods, and in particular this must include the 20th century.
And to note myself I doubt that france does in fact surrender all that much in comparison to other countries and especially if one attempts to compare to equivalent situations. But my opinion on the subject is far different than making the statement that it just isn't true.
I am planning a switch from software development to IT consultant role once my MBA is finished. I still have 2 years to go and in a position where I need to select my electives for 3rd sem. I am now starting to do research, what all options are there for software developer to move into consulting. Will it be a difficult move and what all challenges I need to face and what electives will be useful. Any IT consultant here who can give bit of advise on this?
How can you be a consultant if you haven't got any practical experience? To be a consultant you really should have a background of problems solved - without that, as a consultant, you're just a warm body occupying a seat.
I dunno: if they are sitting down you can find the buggers - and then the lack of useful knowledge is exposed...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
I always thought the term consultant meant unemployed.
And still they take fatter paychecks... haha Well I always thought the same but as now am pursuing MBA, I can actually see the importance of consultant which we software engineers don't usually understand.
For me at least, I want be out there instead of sitting in front of computer and coding day in day out.. Saying that, I will not get rid of programming so easily. I have plenty of my own projects that I can work on..
How can you be a consultant if you haven't got any practical experience?
And how will you get that experience ? You have to start somewhere. I am working as a software developer but at my free time I have offered my companY to help them solve Business/Finance/IT related issues. And also pursuing MBA from one of the top business school helps. I think if I plan properly I can get enough experience to land into top 4 consulting company after I graduate. But still not sure what roles can I look for as a I don't want to leave IT and want to use both (Software Egineering & MBA) degree in my next role.
You get that experience by doing the pre-consultancy jobs. I have seen many companies that have flown in these "fresh out of university" graduates and I have yet to see one who has had the experience to back things up when it all goes pear shaped. The best consultants I've ever worked with have all had extensive business exposure beforehand.
"Consultant" is so vague a term, and may actually be understood very differently depending on whom you are talking to. In our company, IT consultants = people who answer the hotline when I have a problem with Excel. I doubt this is what you are planning to do as a job.
So first piece of advice : know what you want to do exactly. Evaluate how much time you would like to code, how much time you would like to do meetings with people, how much time you would like to try and find new contracts. This will then define what type of consultants you want to be. I was being sarcastic in my other post about consultants being useless meat, but good consultants are precious - I use them here sometimes to introduce organizational changes, just because the ideas are taken more seriously when coming from someone with a tie who is not from the same company. But I digress, good consultants can really be helpful if they bring a lot of experience with them. I'd never hire someone with <10 years business experience if I want to get support on a project organisation. I might hire someone with 5 to 10 years experience if I, for instance, only want technical help.
Second piece of advice : be prepared to sometimes do the wrong thing. Consulting is a business, and you should prepare for the case where the customer decides against your idea and you have to implement what he wants.
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
Consultancy isn't about technical skill, it is about business skill.
Can you talk to people? Can you respond politely even when someone (customer) is bordering on being abusive? Can you sell yourself? Can you create a plan that allows you to make money? Do you know how to structure contracts to insure that you will be protected from legal actions. Etc...
You will not succeed unless you succeed at the business skills. But, even if your technical skills are lacking you can still succeed if your business skills are good.
As for the other comments that seem to suggest you don't have enough experience, even if that were true, there are many small businesses that need a bit of help and can't afford a highly skilled person.