Use the tools they provide you. It will be easier, otherwise you will be constantly fighting differences between your version and everyone else.
As a professional using a different os shouldn't be that big of a deal. There is a bit of a learning curve, but there always is when you join a new company.
What editor do you use? You can probably find something similar on windows. Pretty much every other tool you need the company will provide
Ask HN: I'm starting a new job as a PHP developer tomorrow
51–60 of 96 posts
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#52Based on your post, my concern is that you will stick out as a "sore thumb" insisting on using Arch Linux in a Windows shop. Basically, you are signaling to your employer and coworkers that you will be difficult to work with. Please spend first 90 days building a good reputation and impression for yourself with your supervisor and coworkers and later use your reputation to drive any changes. By insisting on using Arc…
They are developing in PHP and don't develop on Linux?
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#53What about the fact that they all are using Windows on the desktop? I'm a Linux person and I can't use anything else. I've been using Linux for 15 years. I asked if they can let me install Linux on the computers, they said I have to use a VM. I'm fine with a VM but I also need my window manager of choice (i3-wm) and so on. Would it be okay if I install Arch Linux on VirtualBox and I fullscreen the VM? What about perf…
Whats the issue here if you are developing php properly you PC is just a way of running x windows so you can login to the sever. They are not developing on individual developers pcs are they.
Is your objection to using win 8.1 for doing documentation in word and using outlook?
Just use win8.1 and use hyperv to run your VM is one option
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#54Your dev environment should ALWAYS run the exact same versions of the stack as production. With PHP, there are too many little gotchas between even minor versions.
Amen brother/sister. You should ALWAYS be working on a dev server set up identically to the test and live servers.
At one place we insisted on having machines from the same production run and ideally all the DASD (disks) would be from the same batch.
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#55Based on your post, my concern is that you will stick out as a "sore thumb" insisting on using Arch Linux in a Windows shop. Basically, you are signaling to your employer and coworkers that you will be difficult to work with. Please spend first 90 days building a good reputation and impression for yourself with your supervisor and coworkers and later use your reputation to drive any changes. By insisting on using Arc…
The company likely has a processes setup around the fact that everyone is running their dev environments the same way. Trying to do things differently without yet understanding their process will only complicate things. For example, at my job everyone runs OS X, so build scripts, etc are all written with that assumption in mind.
Your developing on individual developers machines - you need to change jobs Stat!
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#56Earlier quoted context omitted.
Have you actually tried VirtualBox? Depending on the underlying hardware, the performance really might not be an issue.
I'm not sure VirtualBox have an edge compared to "native" Hyper-V. If you're running windows 8.1 pro (which would be the sane choice, before 10 arrives) -- you have to change the boot options[1] if you want proper hw support for VirtualBox. Changing from Linux to Windows is indeed rather painful. As others have mentioned, depending on deployment/process etc -- you might still be better off trying to live on the windo…
You can migrate Virtual box vm's to hyperv which works very well.
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#57Your dev environment should ALWAYS run the exact same versions of the stack as production. With PHP, there are too many little gotchas between even minor versions.
Amen brother/sister. You should ALWAYS be working on a dev server set up identically to the test and live servers. At one place we insisted on having machines from the same production run and ideally all the DASD (disks) would be from the same batch.
Eh. Sometimes variety is nice. Exposes some new bugs sometime.
If your tools are sane, dev how you want.
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#58Based on your post, my concern is that you will stick out as a "sore thumb" insisting on using Arch Linux in a Windows shop. Basically, you are signaling to your employer and coworkers that you will be difficult to work with. Please spend first 90 days building a good reputation and impression for yourself with your supervisor and coworkers and later use your reputation to drive any changes. By insisting on using Arc…
They are developing in PHP and don't develop on Linux?
PHP has built in support for ebcdic. It's bigger than nix.
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#59Earlier quoted context omitted.
The company likely has a processes setup around the fact that everyone is running their dev environments the same way. Trying to do things differently without yet understanding their process will only complicate things. For example, at my job everyone runs OS X, so build scripts, etc are all written with that assumption in mind.
Your developing on individual developers machines - you need to change jobs Stat!
I'm developing on the company's machines. Why would that be a problem?
They created an account for me on the Windows machines. I'm on my way to set up an Arch VM.
Re: Ask HN: I'm starting a new job as a PHP developer tomorrow
#60Earlier quoted context omitted.
The company likely has a processes setup around the fact that everyone is running their dev environments the same way. Trying to do things differently without yet understanding their process will only complicate things. For example, at my job everyone runs OS X, so build scripts, etc are all written with that assumption in mind.
Agree with you 100% and that is the point of my comment. Understand the tools, workflow and processes used by the employer first.
I'll do that. I've already asked what they use for their stack, they mentioned they don't use any PHP frameworks.
They mentioned they use OOP and things like that, but their codebase appears to be plain PHP with no frameworks.