|
Ian Shlasko wrote: Try to get Edge to use Google instead of Bing...
It's not completely obvious, but this should do it:
- Open Google in Edge;
- Click the "..." button, and select "Settings";
- Scroll to the bottom and click "View advanced settings";
- Scroll down to "Search the address bar with", and select "<Add new>" in the list;
- Under "Choose one", click the entry for Google, and the click "Add as default";
- Close the settings side-bar;
It took me a while to realise that you had to visit the search engine in Edge before it would appear in the "Choose one" list. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: It took me a while to realise that you had to visit the search engine in Edge before it would appear in the "Choose one" list.
Ahhhhh... That's why it wasn't listed... Ok, might try that. Thanks.
|
|
|
|
|
It's a very slow, very annoying process.
I'm still doing extra overnight disk images every night while I wait for the notification to go "Ready to install".
Sigh.
But...since I hear some people have lost networking, apps, and data in the upgrade, I want to wait until I get the "officially ready for you" version rather than download the ISO myself.
Mind you, Win7 is still running fine, so I don't need the upgrade anytime too soon...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
If you are still waiting for the ready message you may be facing the same issues as me. Have a look at your Windows update history for messages such as
Upgrade to Windows 10 Home Failed
Of course, why it failed is a total mystery. I downloaded the .ISO to do it manually. As mentioned before, my wife's 8.1 system upgraded itself in no time and without problems.
|
|
|
|
|
I had 3 'Upgrade to Windows 10 Home ... Failed' entries. Searching the internet eventually gave the answer that this message is misleading. It means that that the upgrade had tried to run without you getting the notification first and the resolution was to wait and wait and wait until a notification came. My notification arrived a week later and ran successfully. Unfortunately, once it came, I could not do a backup first (but my previous backup was done as close as possible to the official release day so was only one week old). Perhaps I was fortunate or perhaps I was one of the silent majority, but W10 loaded OK (including drivers for a disconnected printer) and works straight out of the box.
My set up is slightly unusual as I had set W7 to autologon (no username / password prompt) so I was a bit worried that it would give me a password and not tell me what it was or would fail to install because that was no longer permitted. In fact, it works - even on W10 it autologs on. Even better, it now allows me to join in the homegroup with another W8 laptop in the local domain. W7 had refused to let me join the homegroup because not having a password meant I was a security risk.
|
|
|
|
|
Was Socrates' busiest student the one with a lot on his Plato?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
No, that was his HUNGRIEST student! 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
Your suck rate just went up. 
|
|
|
|
|
You are occamsionally right, however, this time I am afreud you are wrong.
|
|
|
|
|
Always a chuckle. Brilliant - love to know where you are stealing these from... 
|
|
|
|
|
I tried to come up with something clever, but I Kant.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
|
I Xeno evidence to the contrary!
|
|
|
|
|
I think this is very important. I'm fine with them not knowing everything. I don't know everything. However, you have to know how to troubleshoot (Google/StackOverflow/CodeProject - etc.) and find your own answers. That is key for a developer/engineer these days, IMHO.
I know Google is very big on this in their interview process (solving problems and troubleshooting).
Edit: I know this is a Leslie topic, but hell, enough is enough!
|
|
|
|
|
So what are you looking for, upvotes? Disagreement?
|
|
|
|
|
harold aptroot wrote: So what are you looking for
Just making a vented comment.
|
|
|
|
|
It's a valid comment. And while Google's 'How many ping pong balls fit in a 747?' type question might have worked at one point, people are now training themselves for these.
The true indicator is how well people construct a mental model of the software system they are working with, and how well they can manipulate that model. If we see an unwanted symptom, what fault(s)/failure(s) in the software can enable that to happen?
I always ask people to explain a system they are familiar with, not because I want to know it, but because I want them to explain how well they do. I occasionally get the 'can't talk about the system at my last job' response, so I ask them to talk about something else - Uni project, hobby project, etc.
People who have great mental models are able to diagnose defects simply by the symptom. I've seen this myself - one guy saying 'It can't possibly happen', another saying 'It has to be an off-by-one error in this part' - and being right.
|
|
|
|
|
NeverJustHere wrote: I occasionally get the 'can't talk about the system at my last job' response
That doesn't fly with me. They should be able to describe the system and how they solved problems in general terms without discussing specifics or infringing on their former employer's IP concerns. In a sense, this shows how capable they are of abstracting the problem from its domain.
Software Zen: delete this;
|
|
|
|
|
That is putting unfair pressure on people: I had to sign a NDA at a previous gig and was handed a lawyer's letter when I left reminding me to keep my mouth shut. Ok, it was probably a bit OTT but I would just tell you I can't talk about that, but I can talk about the one before that. What would be the problem with that?
|
|
|
|
|
Any previous project would do, but there are damned few jobs that you can't at least say something about it. Even back when I was a contractor for the DoD I could describe projects in general terms and the problems I solved on my resume and in interviews without violating the terms of my security clearance.
It's a judgement call on your part. If your prior employer specializes in XYZ business intelligence modelling, and you're interviewing with a company that does WXY business intelligence modelling, then you need to be more circumspect than the case where they want you to write microcontroller code for widgets.
Again, it's a question of how well you can abstract the problem from its domain, reason about the problem, and determine an appropriate solution. Being able to retrospectively analyze a project shows your ability to learn from past efforts and apply those lessons to future tasks.
Software Zen: delete this;
|
|
|
|
|
I understand (and agree with much of) what you are saying, but if I say to you I can't talk about that project, I don't think you should press someone or mark against them for doing so. Let them talk about something that doesn't make them feel uncomfortable. If you pressed me to do it, I would end the interview.
|
|
|
|
|
Agreed. My concern is that I've interviewed a couple of people who were vague about everything they had worked on previously. It wasn't that they didn't want to talk about prior work, it was that didn't know how.
Solitary programmers may be able to work without communicating what they're doing, but in my environment you must be able to communicate.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: My concern is that I've interviewed a couple of people who were vague about everything they had worked on previously. It wasn't that they didn't want to talk about prior work, it was that didn't know how.
Fair point. That is hard. I prefer to talk about personal projects when asked. It also shows that I have an interest outside of work and am trying to keep my skills current. Well, I mean, of course I don't count the Lego project... 
|
|
|
|
|
Gary Wheeler wrote: It's a judgement call on your part. ....
Again, it's a question of how well you can abstract the problem from its domain, reason about the problem, and determine an appropriate solution. Being able to retrospectively analyze a project shows your ability to learn from past efforts and apply those lessons to future tasks.
Yes, but unless the programming job requires a legal background it shouldn't be a requirement that the interviewee must be able to determine what it is legal for them to discuss and what isn't.
Now if you want to pay for them to bring their own lawyer for consultation then that then becomes reasonable. Is that is what you are going to do?
|
|
|
|
|
I was once worried enough about an NDA to consult an attourney. Turns out NDAs are not very enforceable on software developers. They are a kind of legal document designed as a pre-emptive strike to scare people who don't know much about NDAs. They don't cover general questions, and they don't cover coding minutiae.
If you were a senior vice president, you should probably not go blabbing your former employers strategic marketing plans. If you were a salesman, you can get into trouble if you steal the customer list. But if you worked for Amazon, the fact that you were working on an e-commerce app that used the cloud, or a portable device running android-ish is hardly a secret. Little fish don't know big secrets. Practically everybody is working on an e-commerce app that uses the cloud. As long as you aren't very specific about the target market, you can talk coding issues all day and not violate your NDA.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
