|
Bobby is dead. I killed him and his friend Bobbi just to make sure I got everyone. 
There have been joys too great to be described in words, and there have been griefs upon which I have not dared to dwell, and with these in mind I say, climb if you will, but remember that courage and strength are naught without prudence, and that a momentary negligence may destroy the happiness of a lifetime. Do nothing in haste, look well to each step, and from the beginning think what may be the end. - Edward Whymper
Climb On!
|
|
|
|
|
And you weren't suspicious when Maunder said "it's been fixed"? 
|
|
|
|
|
Thanks for the first laughter of today! 
|
|
|
|
|
Give me your login credentials and I'll have a look at it 
|
|
|
|
|
First, please prove to us you do not have multiple personalities.
cheers, ~o:37;
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|
|
Impossible. It's already been proved that I do. But since denial is the first sign of a problem... I don't hear voices at all and I haven't been two people since the fight in the kitchen with the paring knife where I killed Bobby he was always, "trying to be heard" and it got old so I stuck a knife in him. For some reason it hurt like hell and I needed stitches afterward but that's how I know it was a knife fight. I'm glad I survived.  
There have been joys too great to be described in words, and there have been griefs upon which I have not dared to dwell, and with these in mind I say, climb if you will, but remember that courage and strength are naught without prudence, and that a momentary negligence may destroy the happiness of a lifetime. Do nothing in haste, look well to each step, and from the beginning think what may be the end. - Edward Whymper
Climb On!
|
|
|
|
|
Maybe it my age showing, but how did the definition of 'Senior .Net Developer' somehow become expanded to include .ASP.Net, jQuery, angular.js, knockout.js, Web services, and other spider abode droppings?
I am currently in the market, and see a lot of positions that are looking for .Net developers: "Hurrah, says I, just what I am looking for" - only to see the first requirements include ASP.Net, some form of framework, and mobile development. Now, mind you , I have no real grievance against ASP.Net itself, been doing it for over 15 years, mixed in with 'real' winforms and backend development but all these 'flavor of the week' javascript frameworks are a pain.
|
|
|
|
|
Pretty much. In a similar situation. They might as well just advertise as "Developer" because every job (even Junior and Mid-level ones I've seen) requires both full .NET and web stack knowledge. The most amusing part to me is most of those positions won't require even half of what they request. And they'll want you to learn the newest xxxxJS library in a couple months anyways 
Unfortunately many of these positions are posted from HR who have zero idea what any of this means so if anyone they talk to about the position even mentions "xxxx or yyyy would be a plus" in passing it'll be put as an absolute requirement on the ad.
Of course this is just my experience. Your mileage may vary.
|
|
|
|
|
Yeah. I swear that someone just checks boxes on an HR form, and it is too much trouble to read the elephanting things, so they check them all....
An elephant: A mouse built to government specifications. - Lazarus Long
|
|
|
|
|
In a twisted way this makes sense. HR's job is to hire people. The technical/project manager's job is to get results. When you need to hire someone the two have to meet. The manager views this as an obstruction - something to be rid of as soon as possible. HR views this as a review of requirements. The manager mentions what they'd like in a candidate in order to optimally meet requirements now and in the future. HR sees this as a strict requirement for the position. The manager is speaking in relative (optimal candidate) terms while HR wants baseline terms for hire. While the manager would gladly accept someone that doesn't strictly meet what they'd optimally like in a candidate, HR doesn't understand this and explicitly searches for a candidate that meets all mentioned requirements.
In the end, if you manage to make it to anyone technically inclined you'll probably get the job. The real hurdle is not getting your application canned by HR whose sole job is to filter candidates based on their presumed requirements.
|
|
|
|
|
stoneyowl2 wrote: all these 'flavor of the week' javascript frameworks are a pain
Unfortunately, that's the way things are, now.
It's become a world where the big difference is between those who think "Hmm, this could be an effective, robust, and perhaps interesting way to do it", and those who go with "Hey, this way, I don't have to do much work!"
Unfortunately, as in every field, the lazy %$#@ers far outnumber the talented.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: and those who go with "Hey, this way, I don't have to do much work!"
Laziness only goes so far; after a while, it becomes an impediment.
|
|
|
|
|
Yup, and then the lazy %$#@ers get promoted, because all they've learned, during their tenure, is how to suck up to the boss to cover their sins.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The web side of things is always hyper inflated!
MVC + HTML + JavaScript is a basic reasonable requirement
jQuery, although use less and less is good to know, just spend 2 hours on it, you will get the idea.
and then an MVVM web API is nice. I prefer VueJS, but hey Knockout of Angular are other candidates. Angular is more like a framework, imposing a development style though.
For styling bootstrap help, and it only takes 2 hours to know all of it.
Then there are other things that are popular that I never used, so one could probably survive without it: nodejs, npm
|
|
|
|
|
Because the people advertising the jobs have no idea ... about pretty much anything.
|
|
|
|
|
Well, I believe things got complicated when we went from making applications that ran on windows, to writing Code that Generates Code that runs in a sandbox on various machines/devices to interact with the user.
Oh, did I mention that the "sandbox" is actually one of MANY sandboxes (IE, Chrome, FireFox, Safari, etc, etc, etc)... Which require libraries (jQuery) to make them look like one unified sandbox (ish).
I thought the purpose of .Net was to fix this? Or was that Java?
Oh look a new device to write for... Gotta go!
|
|
|
|
|
My favorite posting with dotNet as a requirement came about a month after Microsoft first released Visual Studio.NET as a follow on to VS 6. It wanted 3-5 years of dotNet experience, which would only have been possible if you had been on the Microsoft tools development team that wrote dotNet 1.0 and VS.
|
|
|
|
|
Stoney,
Since you mention job postings, I wonder if this is venting due to you having some issues with your job search? I am a lead developer/manager on the web applications team for a company, but these comments are all my own and not representative of the company I work for. I write the job postings for our openings and manage the entire interview process. I have a masters in Computer Science and have been professionally developing for about 10 years now, so I'm not an "HR" type. Despite that, I do include most of what you mentioned on my postings as well.
The reason being, and as mentioned further down the thread, these frameworks do not take long to learn but the mindset that you need to write good web code is completely different than desktop development, and is quite a bit different than mobile development as well. Even the differences between the Web Forms and MVC approach is considerable. jQuery, angular, web services (WebAPI or WCF) are all part of the microsoft stack now, as is Bootstrap. Even node.js to some extent. You may be able to find a job that just uses pure ASP.NET (prior to MVC), but if you are using the latest version of Microsoft's web tech stack, most of the above will be included.
All of these are just toolsets and means to an end. When I interview, a large component of our process is several real programming tasks. The MVC challenge is done offline before you come on-site which will give you the opportunity to learn the right way to do the task and implement it as such. It has components of everything I mentioned above. When you are on-site, we do a live coding exercise where you are given a problem description and have to go from a text document to a functioning application that meets all requirements in the span of an hour. This is a console application and doesn't include any web functionality. This gives us the opportunity to see how you think, how you deconstruct the problem, how fast you can implement it, how much and how effectively you use online resources such as Stack Overflow... It is surprising how enlightening this component is and makes me surprised that more companies don't do something similar. Remember, an interview is many-faceted. It is not strictly on your ability to develop software in a vaccuum but is on your ability to do the job interviewed for. In many cases in the software development world, this requires a growth vs fixed mindset, interpersonal communication skills, ability to gather and document requirements effectively, etc.
I don't so much care that you have used Angular before, or WebAPI, or whatever. I care that you can see the value in these technologies and are excited to learn them and use them. From your post, it seems like that's not you, and that could severely hamper you in an interview. I'm not going to pass on your resume because you didn't use any of these components at previous positions, but I'm going to expect that you've read about all of them and can speak on them when you are interviewing with me.
That's really what the job posting is for, a tip-off on our tech stack and a cheat sheet to prepare for the interview. We do not require that you have used every technology, but our language is similar to "Familiarity with all or some of the following" to tip you off that you should become familiar with these.
If you confuse Java with JavaScript, or think node.js is a client side framework, it will be pretty obvious that you don't care enough to prepare for a position where these technologies are used, and are comfortable in knowing what you know and not a whole lot else. Maybe this isn't you, I don't know you. I am just commenting in a general sense in the hope that it might help you see where we are coming from on the other side of the fence, and possibly some beliefs that could be holding you back on your search.
One parting comment I would make as well - these technologies are quite clearly the way of the future for Microsoft. .NET Core is similar in many ways to node. npm and nuget are essentially the same. the cross-platform nature and hosting of Kestrel+C# (outside of IIS) is just like node+javascript. In fact it could be argued that it's a better version since C# is a better language in many ways and Kestrel outperforms Node. Microsoft is focusing on container technologies moving forward with Windows Server 2016 and the Docker partnership. The purchase of Xamarin and open-sourcing of .NET are major signals that MS doesn't want .NET to be tied directly to Windows.
The landscape of our tech stack is experiencing a seismic shift right now and I for one am excited to see where it goes. I tend to hire people who have a similar mindset.
|
|
|
|
|
I don't recall who it was who ebulliated over the release of a boxed set of Person of Interest, but it inspired me to send off for a set (and then spend an eternity ripping the discs to add Chinese subtitles), but it was a good call.
Impressed am I the show with, thus far, so Cheers!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
POI was a good show; enjoyed the character development, and, being in a tech environment, can see how things COULD progress.
|
|
|
|
|
From what I've seen so far, it's extremely well thought out, so much so that it could even fit under my Real Futures(TM) umbrella, and the characters are brilliantly written, in that they actually think and behave as more than the usual cardboard cut-outs that US TV is riddled with.
It's nice to see good people (which 99% of people are) trying to do something good with their lives (which 99% of people would do, if they weren't so busy just trying to survive).
Lots of kudoses to the writers*.
* Of the first season, at least.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
We've watched the entire series via Netflix; both my wife (non-techy) and I (techy) enjoyed it.
|
|
|
|
|
Hi All,
First post here. Hope this is a suitable subject. You've no doubt all noticed that AI is the flavour of the month on numerous web sites and media outlets but I'm wondering (based on my current personal experience discussed below) if it truly is as far advanced as the hype would have us believe.
Recently I've been working on a personal project to attempt to summarize into a very simple form the remarks of stock analysts on specific stocks on a Canadian TV show. Amongst other things, I want to identify the stock & figure out if the remarks were +ve, neutral or -ve (i.e. their "sentiment"). I've been using NLP tools from Stanford & Microsoft Cognitive Services (MSC) as part of a C# .Net program. Using the Stanford sentiment API, I have trained a model on a set of about 900 plus sentences & about 3000 business word rated as + or - by other. After about 4 iterations I have about 90% accuracy on the training set & near 80% on a reserved set of another 150 sentences. Seems OK but, for example, "Stock's Up 180% This Year" & "The Stocks Are Doing Well" are still rated as neutral and "I'm Very Cautious On The Utility" is rated as positive! I haven't spent as much effort on the MSC sentiment tool but it did not do too well on a limited test. For example, "It's Underperforming The Market" gave a score of 0.82 which is very positive in the Stanford rating system. Overall, there does not seem to be that much "intelligence" at work in these classifiers despite words such as "deep learning" being mentioned.
Sorry about the length of post required to provide context. Any thoughts on this topic appreciated. Am I expecting too much or am I missing something vital that take things to another level? Regards, RB
|
|
|
|
|
Nice to know. Maybe you write someday a series of in depth article about it.
But I think the AI isnt now so well developed. Even on 90% means that every 10th information gets wrong interpreted. Nice for "small talk" but not suitable for "Rocket science"
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
80% is about expected, you can get a bit more with more data.
There is no other level (yet).
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
