You were claiming that "[Adobe] have an EXCELLENT record on is letting you run it anywhere". This source and it's linked bugs show that this is not true for many people. That is what I claim, don't twist my words.
yes Adobe hasn't got even a good much less great security track record but one thing that have an EXCELLENT record on is letting you run it anywhere
Apart from Linux platforms based on these processors:
* Intel Pentium III Coppermine
* Intel Pentium III Tualatin
* Intel Celeron Mendocino
* Intel Celeron Coppermine-128
* Intel Celeron Tualatin-256
* Intel Pentium M
* AMD Athlon XP
True; when you have the chance visit the museum right around the corner. Take one of the Docent tours, ours was great, they have tons of stuff to show.
DECT is a littler harder, but apparantly still doable.
Every encryption is 'doable', but saying it's just a little harder is an understatement.
BTW: DECT is finally coming to the USA, which is a Good Thing(sm)
It's awesome what you can do with a wingsuit. Cruising through the air busting clouds. You can really cover some distance, like crossing the Strait of Gibraltar crossing the Strait of Gibraltar. There is a lot of development going on, at BirdMan, Inc., Phoenix Fly and in cooperation with ie. Go Fast and the Soul Flyers with Salomon Sports . Have a look at the photo's and awesome videos.
I think you've overlooked a very important line in the story: ...although my boss does produce some code and is the reason that I would like version tracking (he has made changes to my code that I was not aware of until I noticed problems with certain functions)...
From this one can deduce that:
Boss codes
Boss thinks he can code
Boss thinks he knows how to run his code shop
As a boss he needs to be convinced he is capable of doing all this, of course, so it takes a lot more than just balls to alter this situation. It takes a sideways approach to the problem, which may result in some interesting solutions...
Having been in such a situation myself a couple of years ago and looking back at it I realized that it wasn't a technical problem or whatever. It's about job responsibility. It very much depend on the way you guys work as a team on the code, even if it's a 2 man team.
If there's an atmosphere of free and open coding, with shared responsibility (both in the mind and when the **** is hitting the fan) then it just has to feel like the way you want to work. If the responsibility is on your shoulders, then without having the control you rightfully claim comes stress. This will come back time after time when events happen. Mild stress when small problems occur, major stress when things come crashing down. It will eat at you time and time again. Recognize this early on (It seems like you did) and set some boundaries for yourself. How much will I put up with? Then prepare a bailout plan. You may need it when the **** hits and you're kick out, or, even better, when you decide it's enough.
For me at that time it was a matter of an ever shrinking development window. It became increasingly difficult to get any requirements from the other departments before the delivery date was due. It was a good working environment, so I informed my boss I didn't want to put up with that any longer. He also wasn't in a position to change that and when the next development cycle was the same I activated my bailout plan. It was a bit scary but I landed a good job, which I still enjoy.
Bottom line is set your boundaries and be prepared to bail out.
Yep, I've contacted Sophia in 't Veld a couple of times on this subject already (as well as her predecessor Ms. Boogerd) and got a reply every time.
At first they personal responses and were rather optimistic. The last one was send as a reply to messages from a whole bunch of people. It glanced over the procedural 'shortcuts' the EC made, while focussing more on further action to take. It didn't respond well to the bitter frustration this dossier created, and tried to make a case for adoption of the EU 'constitution', by stating that this would make the whole process clearer. Well, the current process is clear enough for everyone to see that we got screwed over and that didn't stop them, so why should a 'constitution'? I can only refer to Open letter to the EU: Constitution, we have a problem
Don't you guys know The First Rule of Electronics: Keep the smoke inside!
One a side note: If it's not on fire, it's a software problem.
Oke, back to work now.
Hop into the nearest internet cafe or booth and mail yourself. They are around everywhere. Cheap, save and simple, with 24/7 data protection (depending on ISP of course:-).
Slashdot Mirror
You were claiming that "[Adobe] have an EXCELLENT record on is letting you run it anywhere". This source and it's linked bugs show that this is not true for many people. That is what I claim, don't twist my words.
yes Adobe hasn't got even a good much less great security track record but one thing that have an EXCELLENT record on is letting you run it anywhere
Apart from Linux platforms based on these processors:
* Intel Pentium III Coppermine
* Intel Pentium III Tualatin
* Intel Celeron Mendocino
* Intel Celeron Coppermine-128
* Intel Celeron Tualatin-256
* Intel Pentium M
* AMD Athlon XP
Source: https://bugbase.adobe.com/index.cfm?event=bug&id=3161034
True; when you have the chance visit the museum right around the corner. Take one of the Docent tours, ours was great, they have tons of stuff to show.
BTW: DECT is finally coming to the USA, which is a Good Thing(sm)
It's awesome what you can do with a wingsuit. Cruising through the air busting clouds. You can really cover some distance, like crossing the Strait of Gibraltar crossing the Strait of Gibraltar. There is a lot of development going on, at BirdMan, Inc., Phoenix Fly and in cooperation with ie. Go Fast and the Soul Flyers with Salomon Sports . Have a look at the photo's and awesome videos.
From this one can deduce that:
- Boss codes
- Boss thinks he can code
- Boss thinks he knows how to run his code shop
As a boss he needs to be convinced he is capable of doing all this, of course, so it takes a lot more than just balls to alter this situation. It takes a sideways approach to the problem, which may result in some interesting solutions...Having been in such a situation myself a couple of years ago and looking back at it I realized that it wasn't a technical problem or whatever. It's about job responsibility. It very much depend on the way you guys work as a team on the code, even if it's a 2 man team.
If there's an atmosphere of free and open coding, with shared responsibility (both in the mind and when the **** is hitting the fan) then it just has to feel like the way you want to work. If the responsibility is on your shoulders, then without having the control you rightfully claim comes stress. This will come back time after time when events happen. Mild stress when small problems occur, major stress when things come crashing down. It will eat at you time and time again. Recognize this early on (It seems like you did) and set some boundaries for yourself. How much will I put up with? Then prepare a bailout plan. You may need it when the **** hits and you're kick out, or, even better, when you decide it's enough.
For me at that time it was a matter of an ever shrinking development window. It became increasingly difficult to get any requirements from the other departments before the delivery date was due. It was a good working environment, so I informed my boss I didn't want to put up with that any longer. He also wasn't in a position to change that and when the next development cycle was the same I activated my bailout plan. It was a bit scary but I landed a good job, which I still enjoy.
Bottom line is set your boundaries and be prepared to bail out.
At first they personal responses and were rather optimistic. The last one was send as a reply to messages from a whole bunch of people. It glanced over the procedural 'shortcuts' the EC made, while focussing more on further action to take. It didn't respond well to the bitter frustration this dossier created, and tried to make a case for adoption of the EU 'constitution', by stating that this would make the whole process clearer. Well, the current process is clear enough for everyone to see that we got screwed over and that didn't stop them, so why should a 'constitution'? I can only refer to Open letter to the EU: Constitution, we have a problem
Don't you guys know The First Rule of Electronics: Keep the smoke inside! One a side note: If it's not on fire, it's a software problem. Oke, back to work now.
Hop into the nearest internet cafe or booth and mail yourself. They are around everywhere. Cheap, save and simple, with 24/7 data protection (depending on ISP of course :-).
+MiniDV is great. Almost broadcast quality (NTSC).
;-)
Who says that NTSC is broadcast quality?