|
All the juniors from my college that I met are crazy about bootstrap and angular and php.
|
|
|
|
|
I graduated four years ago from college -- and all I have been able to get are interviews for 5+ years to Senior Level roles. Nobody works with people anymore to train, Companies don't want American workers to train they all outsource Director and Sr. level roles from India, Russia, Pakistan, then that manager hires young people from his country.... Seen it for years. There is NO shortage of Jr. roles just a shortage of jobs because they are all being booked by foreign workers. Government, Silicon Valley, Microsoft, it's everywhere!!!
|
|
|
|
|
The general thing is to hire a mid-level dev on a junior devs salary - Seems to work when people are struggling to find jobs
-= Reelix =-
|
|
|
|
|
Do you reference other projects or do you reference the assemblies from other projects?
I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
If they are all in the same solution then I reference the assembly(DLL) as that is what is suggested in VS2015.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Not sure I agree, but maybe I don't understand what you mean.
|
|
|
|
|
Usually I reference the project so I can debug into it. Once you've made a release build and deployed it it doesn't matter how you set it up in the VS.
What I have run into (many times) is accidently referencing a DLL that's installed in the GAC and then wondering why my changes aren't taking effect.
|
|
|
|
|
I'm with PIEBALD on this one, reference the project so you can debug into it.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
+1 reference to the project
|
|
|
|
|
Why would I want to reference just the dll if I have access to the project?
I'm only seeing limitations.
|
|
|
|
|
suggest it for future polls? Poll Suggestion Page[^]
You will probably get more people answering than posting here
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I thought you could just create a poll. I'm sure I did, once.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Maybe it was like that... then
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
"There were eight-teen of us livin' in that septic tank!"
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Reference other projects because the referenced dll will reflect the changes made from other projects automatically when rebuilding the solution. Unless if you want other developers not to edit the code directly from other projects(core project or business logic) referencing the assembly is the way to go.
|
|
|
|
|
It depends.
If the "other project" is a utility set that is shared by other solutions, then generally I would reference the assembly.
If it's going to be changed as the current solution evolves, then I reference the project so I can debug through.
My general rule is simple: if it's external to the solution then I reference the assembly - and "upgrade" to referencing the project if it becomes necessary. That way, my changes are not risking other solutions which may depend on something working the way it does now.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
Both links are DoA.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
They work fine for me.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Weird - they both return 404 errors for me.
What IP address is your DNS server returning for the domain? I'm getting 129.97.140.120 from Google.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
That's what I get using tracert.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Getting the same using tracert.
But the five last nodes before 129.97.140.120 gets a time out.
|
|
|
|
|
I'm not getting a timeout, just a 404 error:
Quote: Not Found
The requested URL /tsp/pubs/index.html was not found on this server.
Apache/2.0.63 (Unix) DAV/2 mod_ssl/2.0.63 OpenSSL/0.9.7d mod_perl/2.0.4 Perl/v5.8.4 Server at www.math.uwaterloo.ca Port 443
I've tried in five different browsers; I've tried it with Opera's VPN; I've even tried from a server on a completely different network. They all return the same "not found" error.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
The gods of the internet have spoken, this site exists but you shall not find it.
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
Looks like the travelling Nagy problem.
"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
|
|
|
|