Skip to main content

Hardware choices

I'm in a quandry (and not because I haven't posted in a while - I have a number of posts in draft form that need to come).

I'm looking at new machines but I'm unsure. Do I invest in a better server to handle better VMs and possibly Hyper-V and then simply RDP into it when needed or do I look at a laptop for more VPCs?

Ideally it would be both - but economics these days limit the potential. Server hasn't been upgraded for 4 years (Dell SC400) but neither really has the laptop (Dell5150)

Platform doesn't matter these days. Thoughts?

Comments

Unknown said…
Laptops are more expensive and not upgradable. I'd buy a desktop unless you actually need a new laptop.

Regarding platform to choose, I'm assuming most of your clients run Windows.

If you do hardware support, and don't already have a mac, you might want to get one. They are getting more popular all the time. Where I used to live, you could find a windows "mechanic" under every shadetree. There was only one company offering mac support, and they didn't do it very well. So I bought an intel mac.

I recently had a friend who got tired of vista and replaced it with ubuntu. After he spent a day struggling to get VMWare to compile on it, he reinstalled vista. Linux is fine for servers, but still not a very good choice for a desktop system.
Andrew MacNeill said…
Hey Brian - ended up with a new laptop after all...definitely necessary but I think I'll still be looking at a new server shortly primarily for VS 2008 Hyper-V.

The laptop is on Vista - interesting for sure. Not sure if I'll go back to XP or not. I have an older machine running Ubuntu right now and it's not bad for someone who knows what they're doing.
Eric Selje said…
Have you considered any sort of hosted solution, or even Azure? I'd like to hear of real world experiences with these.
Andrew MacNeill said…
Hi Eric- not really interested in a hosted solution - although a colleague did offer one up.

The problem with hosted is that I have to ensure internet connectivity at all time.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...