Notes from my day to day Java and J2EE software development experiences and other related software development technologies.
Monday, February 6, 2012
Visual Rendering with Javascript
Roman Cortes published this great blog post on how he rendered a rose in under 1kB of Javascript! Incredible!
Friday, December 2, 2011
Computer Professionals Update(CPU) Act (S1747)
US developers (especially contractors) should read the new law working its way through the Senate. It relates to the how the Department of Labor classifies developers, DBAs, and other computer professionals.
S1747 Computer Professionals Update Act
As a contractor, I have been affected by the existing rules multiple times, and it is an entirely frustrating interference between the government and the client/contractor relationship.
Consider this... time and material contractor Joe goes to work at the big regional utility. He joins as a contractor for X$/hour. Joe does a great job and is on a large project which after 2 years at the job, regional utility gets nervous about facing fines from the DOL because Joe may be "misclassified" and is being treated as a full time employee without benefits. Joe was happy and the utility was happy. There was no reason for Joe or the utility to stop the existing relationship except for the threat of a lawsuit. The utility tells Joe he has to leave but can return at some point in the future (usually months later). Joe is out of a job, and utility loses a trained worker. These existing rules are convoluted to say the least.
Here's a great article about the law written for the Association of Corporate Counsel.
S1747 Computer Professionals Update Act
SEC. 2. AMENDMENT TO THE FAIR LABOR STANDARDS ACT OF 1938.
Section 13(a)(17) of the Fair Labor Standards Act of 1938 (29 U.S.C. 213(a)(17)) is amended to read as follows:
‘(17)
any employee working in a computer or information technology occupation
(including, but not limited to, work related to computers, information
systems, components, networks, software, hardware, databases, security,
internet, intranet, or websites) as an analyst, programmer, engineer,
designer, developer, administrator, or other similarly skilled worker,
whose primary duty is--
‘(A)
the application of systems, network or database analysis techniques and
procedures, including consulting with users, to determine or modify
hardware, software, network, database, or system functional
specifications;
‘(B)
the design, development, documentation, analysis, creation, testing,
securing, configuration, integration, debugging, modification of
computer or information technology, or enabling continuity of systems
and applications;
‘(C)
directing the work of individuals performing duties described in
subparagraph (A) or (B), including training such individuals or leading
teams performing such duties; or
‘(D)
a combination of duties described in subparagraphs (A), (B), and (C),
the performance of which requires the same level of skill;
who
is compensated at an hourly rate of not less than $27.63 an hour or who
is paid on a salary basis at a salary level as set forth by the
Department of Labor in part 541 of title 29, Code of Federal
Regulations. An employee described in this paragraph shall be considered
an employee in a professional capacity pursuant to paragraph (1).’.
As a contractor, I have been affected by the existing rules multiple times, and it is an entirely frustrating interference between the government and the client/contractor relationship.
Consider this... time and material contractor Joe goes to work at the big regional utility. He joins as a contractor for X$/hour. Joe does a great job and is on a large project which after 2 years at the job, regional utility gets nervous about facing fines from the DOL because Joe may be "misclassified" and is being treated as a full time employee without benefits. Joe was happy and the utility was happy. There was no reason for Joe or the utility to stop the existing relationship except for the threat of a lawsuit. The utility tells Joe he has to leave but can return at some point in the future (usually months later). Joe is out of a job, and utility loses a trained worker. These existing rules are convoluted to say the least.
Here's a great article about the law written for the Association of Corporate Counsel.
Tuesday, October 11, 2011
Open Source XWin Solutions For Displaying Remote Clients
Recently we built a nice desktop interface using Groovy's Griffon to
manage several back-end tasks. The idea was that data center and other
support folks don't want to figure out our scripts/code and that we
would provide a nice friendly interface to manage the complex tasks. So
far so good, until we had users who wanted to keep the application on a remote
Linux server and still have pretty GUIs locally. Nonchalantly, I recommended X11
(ahh its like 1995 all over again only this time better tools!). Umm
yeah... well it took me over an hour to figure out how to make it work
and how to make it work for free, so that's enough time for me to want
to write down the steps so that I don't need to repeat researching this
in the future.
Steps:
Steps:
- Download Cygwin via the Cygwin.exe installer!
- Select the xinit app under the X11 libraries. The dependencies should be downloaded after being prompted to do so.
- Select openssh from the Cygwin libraries
- Open a Cygwin console. Type startxwin. More details on Cygwin/X can be found here.
- Install xauth on the remote server. I am using RedHat so all it required was 'yum install xauth'. You may also need to tweek the X11Forwarding setting in /etc/ssh/sshd_config file to allow X11 forwarding.
- type 'DISPLAY=
:0.0' on you local machine
- type 'export DISPLAY' on your local machine
- ssh -Y username@remotehost (use -v option if errors occur)
- Start remote app.
Tuesday, October 4, 2011
Subscribe to:
Posts (Atom)