Peter Lenahan Email & Phone Number

2 Penn Plaza, New York, Ny

Managing the security project to address possible software vulnerabilities in the WebFocus product line. Managing the Continuous Integration project, for the WebFocus Client.Managing the Search project for WebFocus Magnify.Managing the copyright and licensing of third party software.Managing the source code Static Analysis projects.Security:Security has emerged as a major problem for all software vendors. While we have been increasing fixing security issues for more than 5 years now, we are constantly finding and fixing new threats.Continuous Integration:We are currently shipping about 16 product releases a year, in different branches. These release would not have been possible without the improvements we made in the Manufacturing processes, and the automated detection of bugs in the software very early in the Software Development life cycle.While no system is perfect, we have come a long way in detecting software problems very early in the development life cycle.Copyright and Licensing:Programmers are constantly trying to cut corners, and the internet has made that very easy to do.However with a commercial product you need to constantly guard against copyright infringement or license violations. Constantly reviewing work of programmers to protect the company from lawsuits.Search:This product is an important strategic feature of the product, The search market place for internal systems is still new and still growing, our product keeps evolving to try and find a market niche.

Greater New York City Area

This project started with an attempt to build a product with Google Corporation.We started with a business relationship with Google to be a reseller of the Google Search Appliance as a means to index databases and stored procedures. A large problem with Stored procedures is that if they are not correctly documented, the reports they generate are often lost as employees change companies. A good part of the work done at corporations cannot ever be found once an employee leaves. Also to access data, people can't find the correct procedures even if the employees have not left the company. This model of the project ran into difficulties because of the Google Pricing model, which viewed data as documents, but databases are not documents, they are records. Google was not willing to change the pricing model, so the first incarnation of the product failed.The Next incarnation of the product used an open source library name Lucene from the Apache Software foundation. We started with the Lucene 1.x libraries, which were working bug had many issues. We upgraded many times as the Lucene 2.x releases came out. We stopped upgrading the libraries at this release level for 1 year as we addressed design issues in Magnify user interface.Work is been ongoing since March of 2013 to upgrade to the Lucene 4.x libraries, and also include a redesign of the User Interface and data output format. The next version of the product will take advantages of the features added to the core search librariesAlthough my primary responsibility was with this project, the upgrading of the prior project on the Production Manufacturing also absorbed my time. I put in place a continuous integration model.Build and Packaging and Install times was now reduced to less than 1 hour. Better notifications to programmers were also added for problems with JavaScript, HTML, XML, CSS and Flex.

Greater New York City Area

Managed the Creation of a Production Software Manufacturing EnvironmentThe internet project had grown, and when we started the Internet project, our staff was very small.But now we had a much larger staff and our internal systems for manufacturing the product were becoming a major hinderance to producing production software. Our Source Management Systems were old, and the different groups had splintered, different managers were not sharing software or coordinating efforts well. We were using three different source management systems, PVCS, Clearcase and Visual Source Safe. Our build process were very complicated and spread across machines with un-coordinated production build times.Nightly Compile failures were major cost issue. Stopping the QA group from working many days. These problems were costing us as much as 300 man days of work lost weekly.Our staff had also become decentralized, with development groups in New York and California.The hardware we were using was old. It would take 8 to 10 hours to compile and create jar files for the WebFocus Client. Un-coordinated builds meant that the shared software was not always correctly updated across machines.Following the builds, it would take another 8 hours to package the software. We did not have processes in place for software before it was returned to the central system, we also did not have any web based diagnostics of build problems. It was a very hands on prioritary way of diagnosing build issues.At the end of the project, we had merged all the software from the 3 Source management systems into a single CVS (Concurrent Versioning System) and upgraded the hardware to Linux. Web based diagnostic pages displayed build steps with their status. Build time was dramatically reduced and errors were now reported to the programmer, either immediately or soon after a code return.To improve the build time, the build process transitioned from a single threaded model to a multi threaded model.

New York, United States

Greater New York City Area

Created a new On Line Analytical Processing (OLAP) tool for data analysis written in Java/ JavaScript and HTML for the browser and in a set of other languages for the server components.

Greater New York City Area

This was a new start up group, to explore if we could create a new Internet based product line.The group consisted of a handful of people.The VAX market place had collapsed, the UNIX market place was not growing.We started with a very basic ideas of moving from Client Server computing.To replace the client with a set of browser based programs in Java and HTML.The Server component was a "C" CGI program.Working with 1 other programmer we designed and wrote the web based Managed Reporting Product, which allowed for shared reporting capabilities in the browser. Web Programming was very new, and HTTP was still under development. In client server computing you had full of control of client software, but with the browser you were limited to the behavior of the browser. Netscape, Sun and Microsoft were fighting for control of the Internet, Microsoft was trying to sabotage Sun development of the Java Language, as well as Netscape's browser. We ran into many problems developing software in this time period. But I did managed to get one issue resolved in HTTP (See the details here) http://lists.w3.org/Archives/Public/ietf-http-wg-old/1998MayAug/0119.htmlThis tag was added to the HTTP protocol because of a request for comment RFC) suggestion which I made. This allows you to named content from the server, instead of the browser deciding what name to use when data is saved.19.5.1 Content-Disposition The Content-Disposition response-header field has been proposed as a

Greater New York City Area

The VAX market place had collapsed, so I moved to the UNIX product Group. Basically performing the same position as I did in the VAX group, but on a smaller scale. Less new feature development was happening in this group. This was more of a maintenance and bug fix group at this point. Even the Unix market place was changing. Vendor consolidation was happening, at one point we supported almost 30 versions of UNIX, the source for each version had diverged. This was a management nightmare. Employee turnover was also happening quite a bit in this time period.At the end of my tenure in this group it was clear that this Vendor based computing model was coming to a close. So I moved to a new development group which the company had just started.

Greater New York City Area

Still working in the DEC/ VAX product.At this point the company was trying to introduce a new Client Server set of software.Initially named FOCNET, it allowed the VAX and the IBM Mainframe to communicate data between the machines. This later became the (Enterprise Data Access) EDA product line, allowing client server computing between many operating Systems.My group expanded to include more programmers as the company expanded.We also took on the project to convert from VAX hardware to the Alpha Hardware.We created an Alpha processor based version of the Focus Product line.Our group also identified bugs in the early pre-release Alpha chip, which had an incorrect counter problem with a move instruction.I also took on more responsibility of dealing with customer issues.I often did site visits to deal with customer issues.I had more that 40 people reporting to me before this marketplace collapsed.

Greater New York City Area

A fairly small group of 7 programmers reporting to me. These programmers worked mainly in FORTRAN, C and VAX Assembly Language.Primarily responsible for porting changes from the IBM Mainframe product to the VAX product.The company model at this point in time was platform based, they would write new features on the Mainframe, and then port those features to the other platforms later. The platforms which IBI supported were: PC, VAX, WANG, HP-UX, AS-400, Tandem, and Several Unix platforms.Although my primary responsibility was on the VAX, I also helped develop feature of the company Mainframe debugging tool "FDEBUG" which was originally written by Jonathan Mark and Greg Dorman.This tool had many debugging features but there were no debugging symbols available.The VAX debugger had symbols, so upon examination of the FORTRAN compiler of the IBM VM/CMS system, I realized that I could add symbols to the debugger, by extracting information from the compiler log file.This build symbol tables to all the local variables, as well as to the variables stored in FORTRAN "COMMON" statements.This dramatically reduced the debugging time on the Mainframe, and is still in use today. more than 20 years later.

Greater New York City Area

Programmer on VAX computers, ported code from the IBM Mainframe environment to the VAX environment. Also wrote VAX specific features for the Focus Product.Projects included the creation of a Compiler to Compile the Focus Modify Language to Machine code.A full screen debugger for the Modify Language.A translation program which allowed data to be moved from a MAINFRAME to the VAX environment. (This was called the IMPORT feature)

New York, Ny

Wrote code for the IBM PC, Languages, 8086 Assembly Language, and FORTRANWrote a Network level 4 Session layer, Terminate and Stay Resident Driver for Nesstar networks.Ported from from an IBM Mainframe to the IBM PC.

Greater New York City Area

Worked on FORTRAN code for the NovaPipe program.This was developed on a UNIX platform, with ports to larger hardware platforms, The business model was to deliver a turnkey Hardware software solution to the engineering market place for structural analysis of heating plants.The program performed analysis for industrial piping design, typically heating system.Showing where to place mounts, hangers and expansion / contraction joints.Two of the programmers, and the marketing manager on the product had worked at an engineering company producing the same product, and they thought they could produce a better product.The older company was all card punched data entry. Their model used a Computer Terminal to enter the data, and a very simple graphics display of the piping system on ADM 3A terminals.Unfortunately the Three Mile Island accident happened a couple of years earlier, and the partners were not savvy enough to realize that the market place for the product was actually non-existent at the time they went to deliver the product to market. Power plant construction was at a down turn in this time period. This was a start up company, which was running on Venture Capital money.An argument between the partners happened and the company failed within 1 year.The company never sold 1 copy of software.The company was very small, It was 5 programmers and 1 marketing person.But it did give me an opportunity to work on multiple computer systems.UNIX, IBM Mainframes, and the CRAY operating system.

Greater New York City Area

Developed a very simple game for the Atari 800 computer.Never made it to market. This was not a school project.The game was written in Assembly Language for the 6502 processor, and took advantage to the dual processors built into the Atari 800 computer.It was a very simple game, there was a single sprite which moved around in a maze, the walls of the maze changed as the game progressed.The game was my first attempt at near real time programming, With events and collision detection.and the coordination of running programs on multiple processors.The Atari had 2 different processors with one processor getting 2/3 thirds of the execution time and the second process getting the bus the other 1/3ANTIC chip and the 6502 chips were the processors on this machine.

Non-Degree Management Training

Bachelor'S Degree, Computer Science And Math, 3.7

Education record