Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Encrypt Everything! (Score 5, Insightful) 129

Regardless if the claim is true or not, all your data and messaging should be encrypted at all times PERIOD! I will gladly accept terror acts for the right to have my data protected and safely stored. Across all my computers and my phone, everything is encrypted when possible, including my emails, which are sent from a encrypted provider, my SMS messages, which are sent encrypted and almost everything else I do. Encryption is a right to not have your data / personal information exposed and one that must be protected, even if that means acts of terror are untracable / untrackable.

Comment Of course you can work on your own projects! (Score 1) 387

Work for the company and work for yourself. I'm compensated fairly well, and I put in a great week of work and long hours for my employer, however, that doesn't mean I won't take a couple hours here and there to work on my own projects, even at work.

If your employer can't tolerate the fact that you might take an afternoon to work on a separate project, then it's a bad work environment and bad work culture. On many occasions, the work I've done on my own time, have transitioned both into the IT and Engineering realms for my past employers.

In fact yesterday, I took a hour off to code for one of my own personal projects instead of continuing to work on what I had started the day off with.

My manager and the company owner, know I do that all the time and they know I work on my own projects even at work, and as long as I finish their work and I get what I need to get done, and on time, they couldn't care what else I do and that's how an effective work place functions.

Comment Re:Windows devs, eh? (Score 1) 360

When I'm doing Microsoft Based development and have to interface to the Microsoft poorly build suite of tools, I can burn Ram so fast it's embarrassing. The biggest problem with Microsoft is that I don't have any control over how the resources are consumed, so my only alternative is to throw resources at the problem. I have a running thread with them, full of screen shoots and logs that show how taxed my system is, and they don't see anything wrong with it or think it's unreasonable.

Using VIM or EMACS is better, by magnitudes, but I can't always use Linux and slim editors, which are my preference.

The problem with a development notebook is that it has to be overpowered to handle everything from low level embedded development, where you can still get by with a P1, and full scale large app development where Ram isn't considered a moderate resource. If I'm doing Matlab development with GAMS and CPLEX running, I can exceed the need for 32 GB of Ram, so it's pretty important to stock a development machine with everything you can.

Comment Re:Good Setup (Score 1) 360

To much tech talk.
8) BYOD is commonly a understood term, if your management team / IT team / Development team, doesn't understand what it means, your in trouble. Even if they didn't , which I'm pretty sure would be grounds to leave the company, if you can't explain it's "Bring your own device", you probably shouldn't work there.
5) Not at all, I've used many different SCM's and all of them are garbage compared to GIT.

Perforce decided to random delete and corrupt several repo's, causing massive data loss.
SVN allowed one of the developers I was working with to delete the root ..... why that's even possible is beyond me.
Microsoft's solution constantly corrupts code commits, to the point they can't be repaired.

1) Mac OS isn't based on Linux, it's based on BSD Unix, which means you don't understand the difference between Unix and Linux.
9) I assume you're joking, but I can't tell, see the first answer.

How much CPU performance do you lose running you beloved Linux in a VM on a Mac under Mac OS X?

I would never do this, because I don't run Mac, but I have no problem with it. Last time I tried this, we lost about 20% of the CPU do the VM and it caused the applications we were running to shudder and eventually crash. However if you look at VMWare or KVM, you'll have the same problem. Virtualization can't only give you less then you currently have.

Virtualisation on the Server is fine, but that's where it should stay. If I buy a high quality i7 computer or even XEON based workstation, the last thing I'm going to do is to throw some type of VM on it and instantly sacrifice the internals, IF I want to the use that computer for desktop work. Again on the server, it's a fine technology and I use it frequently.

Hint: a person can not notice the difference. Even if you would utilize the CPU(s) 100%, you barely would be able to quantify the difference over the course of a few days.

I could test this right now using Virtual Box, and if I boot up a Windows 10 VM, then try to load Visual Studio 2015, Altium Designer, Excel, Word, MySQL Workbench and a few other apps, that VM will be grinding, to the point I can't use it. If I boot that natively without Virtualisation, I might be at 80% of my CPU, and 30% of my RAM (this computer has 64 GB).

Comment Good Setup (Score 5, Interesting) 360

This would be my recommended list:

1) Give them the choice of OS, Linux or if they have to suffer, Windows / Mac.
2) Unlock the notebooks so they have absolute full control of them, that includes admin accounts.
3) Stop using Ultra-books, use high end notebooks with loads of Ram, good M2 / SSD Storage and high end processors.
4) Don't use any kind of virtual environment, they just have no performance to offer and should never be used in a desktop setting.
5) Open the development tools and let them use what they want.
5) Standardise to GIT for the SCM, as it's the only good SCM tool on the market.
6) Use good team communication tools.
7) Try to steer clear of Microsoft based tools, for instance TSF, it's a giant pile of steaming shit.
8) Allow BYOD.
9) Give every developer a multi head setup with good keyboards and mice, this never gets acknowledged, but a good Mechanical keyboard is essential.
10) Every developer should have a stand up desk, that can also covert to a sitting position.
11) All the developers should have isolated build servers, that they have near full control over, maybe not the root account, but damn near.
12) Don't allow IT to dictate how the computers for the developers are used.
13) Buy high quality chairs that are designed for long work sessions, they can be pricey but they're worth it.
14) Allow developers to have full flex time, so they don't have strict hours, they can work 8 hours over the course of the day.
15) Don't allow management to over plan meetings.


Basically treat the developers like the rockstars they are.

Comment Not even (Score 0) 92

Blackberry stands for bad interface design, bad user experience, poor build quality, poor application quality and an over all lacking phone experience. If they want back into the phone market, they need to deliver a great phone, not a bad phone over hyped and drastically under delivered.

For instance, the passport has got to be, one of the worst concept phones of all time, hands down. It's size made it unusable in any efficient manor, it's software stack was buggy and crashed. It's included applications would of been a sorry excuse for a kids product and forget about that insane hub idea / user interface. The passport was so bad, that it can't be recovered from.

When I worked at Blackberry as a application prime, I once tried to hold a build of the OS because some of the application they wanted to bundle into the build were so buggy and so poorly built, that would of made people throw the phones out. My manager overrode me, pushed the build and one week later almost all the carriers rejected it as total crap.

Blackberry is a company with no standards and no quality behind it's name. Until they can deliver a great phone experience, which would be the first time in a over a decade, they have no right to even be considered a contender.

Comment Re:Simple Answer (Score 2) 119

Each port on the network switch should of been MAC bonded and then if someone connected an unauthorized device, it would of shut down the port and thrown an alarm with the offending MAC address, which can then be traced to the device being plugged in. This is exactly how I handle all the switches in all my networks.

Slashdot Top Deals

"There is no statute of limitations on stupidity." -- Randomly produced by a computer program called Markov3.

Working...