I noticed its only for text only rants. If there are images, you will not see the problem.

that

Ow.

Split keyboards maybe? Are they going to immobilize your entire arm? I would be more worried about going to the bathroom than coding haha

It took a couple of weeks for mine, but they did come. I am in the US though, so it could take longer.

It is a very small group of people at devRant so you have to be patient for the goodies.

Lived in a non-technical house growing up. We had a Tandy 2000 until I was 15: https://en.m.wikipedia.org/wiki/...

After that, a pentium 3 NEC desktop.

And... they sent me an offer? It was a 6 hour interview with only one of them going to the "I know far less than I think" territory.

I would love to work with the guy who did the last portion of the interview. He was the who made me feel inept. I need to learn how to read people better I think.

Interested in seeing where this goes.

I write my code thinking of a quote from a book about Perl I saw once:

Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live.

That was fantastic advice. I have worked with many devs who didn't see the benefit in automating as much as possible when it makes sense. I don't know him, but I like him just based on what you have put in this post.

Usually a psychological and reasoning evaluation.

When I saw this I heard the sultry tones of Scott Allen for some reason.

@arekxv I am fine with your difference of opinion. In my world, Inline sql is bad in a lot of ways. You are correct that query caching does exist when you fire any query against certain rdbms's however, having to recompile code and redeploy it to production makes it difficult in my environments that I work in. Additionally, the security auditors get itchy when they see any dynamic sql written in source. Now, if you use EF or nHibernate you can accomplish the same thing as inline sql with the advantages of having the query logic in your code. I am not saying that there is not a place for inline sql, there is, I just don't think that in the conversation that I was having with this architect that what he was trying to say was relevant to the subject matter we were discussing.

Inline sql is bad for a lot of reasons in most major languages. It poses a possible security vulnerability (old PHP was known for this) and it does not take advantage of the rdbms query caching. Even though it does exist and is known to be around in a lot of either code which is currently in development or old insecure code you should avoid it whenever possible. You should use tools such as the Entity Framework, nHibernate or logic stored in the database (stored procs, functions, views...etc.) whenever possible.

Its an owasp top 10 vulnerability: https://owasp.org/index.php/...

It also is indicative if half baked code in a lot of situations.

The most common tests you get are take home style tests. In those the company will usually ask you to write a test project that handles some abstract scenario (E.G. project to handle widget production in a factory).

Another common test is "pair programming" with a developer from the team where you are assigned a task and you both work on solving it together. This is common in larger companies for more senior level roles, not usually a jr. Level interview.

The least common scenario is the whiteboard (which I have never had to do personally). In this scenario they ask you to write a program on the whiteboard with just a marker and a blank board.

Usually, for junior development roles I have seen and administered interviews where we get a sense of who you are and what your mindset is. There are general javascript questions (e.g. what is an anonymous function, what is the scope of a variable, is javascript multi-threaded). But, we usually are trying to figure out how you think.

I went to school for mechanical engineering and I can say that people think about mechanical engineers the same way that most people think about software engineers.

To software engineers:
"Hey, can you help me fix my computer?"

To mechanical engineers:
"Hey, can you help me fix my car?"

I wonder if chemical engineers get: "Hey, can you help me mix my meth?"

This makes me feel like I drank a cup of warm hot chocolate.

You, my friend, have made my day... nay... WEEK!

http://i.imgur.com/HmNTxGX.jpg

Honestly, a degree can be very useful for unrelated reasons than knowledge for your specific job. College is a great way to really understand how to learn independently and to find out what drives you.

Now, for finding a dev job, having a degree makes it significantly easier to get your first job as a software engineer with no experience. However, a degree usually doesn't prepare you to be, or make you, a good developer.

With that said, almost all of the best software engineers, architects and developers that I have worked with did not have computer science degrees. They found out they loved doing this either in or after college. A smaller number of them never went to college and were self taught.

College is a good thing for almost everyone. Computer Science degrees, in my opinion, however do not prepare you to develop.

I actually suggested it. They didn't know it was an option.

It had been tested by QA when the app had launched, but the indexing jobs had been failing for a long time. So the indexes which were being affected in the db by the functions inside the cursor became very very fragmented. That meant the sproc ran slower than a snail covered in super glue. Needless to say it started to timeout and the process failed to complete.

Cursors make me sad when they are used in this way. Cursors almost always make me sad. Almost as sad as when I see triggers.

I feel like I should be able to give more than 1 "+1" for this.

I listen to 10 hours of babies crying on youtube on a loop with ASoftMurmur and some H.P. Lovecraft book in the background.

I don't reccomend it.

Dead baby jokes live in the deepest recesses of my previous companies source where I was working alone for months upgrading a system that has not been updated since I left.

I am still waiting for my friends who still work there to tell me that they have found them.

I did that 4 years ago.

nightmares from both.

Firmly entrenched in camp sequel here.

Better means more money and a higher title.

I love the people I work with, not the money though.

Present.

As with everything it depends on what the project is written in for me. My go to's are usually anything JetBrains for stuff outside of .NET and obviously Visual Studio for the .NET languages.

For database stuff I stick with SSMS for MSSQL Server, datastudio for DB2 and just the workbench for MySql.

P.S. Eclipse development is what I picture hell is like.

I sometimes wonder if I am that guy.

emes001 I plan on staying in both but I wanted to expand my knowledge base and wanted to see if there were any gotchas before I dove right in. I'm interested in the compute side of things and want to see if AWS offers a better solution than Azure.

Is there anything I can setup without a VM or should I just start there and move forward using exposed services in AWS within that provisioned VM?