A month or so ago you completed your acquisition of Twitter, a social media platform. Not a software company, not an engineering company, a SOCIAL MEDIA platform. You have laid off over half your staff and with your ill worded ultimatum, the remaining half of your staff left as well.
In the meantime you have been holding ‘code reviews’ which are pointless in terms of fixing what is wrong with twitter. You then add a cherry to the top of the crap cake and allow a known traitor, Trump, back on your platform. I have been an engineer, a real, degree engineer, for 24 years and I can tell you are not facing a technological issue, you are facing a psychological issue.
I am part of your target audience, a late 40’s, white male, and I abandoned the platform even before you announced your acquisition earlier this year. Why did I leave? It was boring and there are better alternatives out there. Too right wing, too full of stupid, and just too boring to top it all off. The major technological gripe was how difficult it was to engage with others. In fact, this loops back to the social, psychological issue with Twitter. It is not compelling. The content is not unique, the whole microblogging idea has been done to death and no amount of software engineering will fix that.
I honestly don’t know how you can fix Twitter. It may just be an idea that has played out, like America Online, Myspace, Geocities and Angellfire. Websites and social media come and gone and it may be time for Twitter to go. When a traditional message board like Reddit or social media like Facebook exist, what’s the point of Twitter? With ad free alternatives like Mastodon, what compels me to use Twitter? All of these points are psychological, not technical. Forget code reviews and hire a team of psychologists, anthropologists, and sociologists.
I would wish you luck, but to be honest, I, like millions of people will not miss Twitter one bit.
Trying something new, by trying something old. I really enjoy digital photography. I never really owned a film camera and am an early adopter of digital cameras, going back to before 1999 with cameras like the JamCam 2.0 and i/o Magic Magicimage 500. That being said, my first ‘real’ digital camera was the Olympus C3000, released September 4, 1999, was a fantastic camera at the time. I picked up a well maintained example off eBay for a song and decided to see how the now 23 year old technology holds up.
As you can tell, for a camera over 2 decades old, it is not that bad. I think the most noticeable flaw is the purple fringing and not processing blue all that great, but this was a very common issue with the CCD sensors used at the time. That being said, you really would not know with the fire hydrant and path photos above these photos were taken with a camera built during the Clinton administration.
All the photos are relatively sharp and my biggest complaint is when taking photos the shutter lag is frustrating. My main camera is a Canon Rebel T1i, and even though it is a 13 year old camera, dSLR cameras shoot almost instantly. In good lighting, the C3000 still performs reasonably well, but the limited ISO range really forces you to use a flash inside or have a very steady hand.
That being said, the photo above was taken on our wedding day, almost 20 years ago, and I am sure am glad I had this quality of camera in 2002. I love going back to our old photos and they are just as clear, sharp, and colorful as the day they were shot.
Here are some more photos taken on the same walk.
I’ll take more photos with some of my other collectables in my collection, along with photos taken with a newer dSLR with very old glass, in some cases from the 1960’s.
After losing a job that I had for 7 years, it has taken a while to really get back to my self, or, a better way to put it is my new self. Getting laid off is very disappointing, but looking back, and looking forward, I am truly in a better place now. My new position is more intellectually challenging, the highest level position I have ever had, and I get paid more.
For those of you out there who have lost a job of no fault of your own, it does get better. In the beginning, you thing, what could I of done better? Why was I chosen? To be honest, I think it was a short sited dollars and cents decision. We were all late on our annual review/raise, and with new owners, I guess they figured it was easier to just cut all the higher paid employees and hope the lower experience/cheaper workers can take up the slack. There is really nothing you could do better. All of my reviews were great, even though the average raises were inflation level, at best.
With hindsight, it really was a good thing I was laid off. Even with great reviews, they were late and the raises sucked. I was getting bored working on the same project for years with no end in sight. Now that I am working again, I saw just how far my skills were wasting away. So far I have completed several tests that have been waiting in the wings for month, repaired broken test equipment, and participated in a new program from the very start, helping with specifications and adding standards. For the first time in a long time I finally feel like I am making a difference with my efforts.
For those of you that have lost your position of no fault of your own, don’t despair, it will get better. In fact, this may a time to start that small business you always wanted. Take some time off, regroup, and whatever path you are going to take will almost certainly be better than the one you were on. Remember, a business that has to make layoffs is, odds wise, more likely to fail in the next few years. This is not to be confused with selective terminations for ‘dead weight’, this is your classic someone drew a line in ledger and decided this is who is getting let go.
I’ll try to keep up the blogging, it is a good way to finish processing what has happened and I have more happy news to report as spring turns into summer.
Now that I am gainfully employed, I bought myself a benchtop CNC.
As my latest toy in my workshop, I purchased a benchtop CNC. With 3D printers all the rage, why did I go with a relatively old for industry, new for home use Computer Numeric Control milling machine? Well, the reasons are numerous; I can’t make printed circuit boards in a 3D printer, and I don’t like the texture of 3D printed items on a home quality 3D printer, I can work with a variety of materials, and have an upgrade path.
My main goal with my CNC milling machine is to create custom circuit boards. For the amount of boards that I want to make, it is really not worth the costs associated with contracting with a board house. If I accidentally create something popular, it will be as strait forward as sending the Gerber files to get made. The file formats that get used for my CNC are the same as the files used by professionals. In the future I will detail what tools I use to create circuit boards. I can fabricate a single layer, 2 sided board in a matter of minutes using relatively inexpensive blank boards.
The second thing that I don’t care fore is the texture and strength of 3D printed parts. I know a lot of it is determined by the type of plastic used, but it still is a limiting factor. I can take an injection molded plastic, like a housing for a controller or joystick and mill out whatever custom patterns I desire and end up with a full strength plastic housing with all the expensive mold work done for me already. The tolerances of CNC are superb as well. Many, if not all, of the molds used for plastic molding were produced on a CNC, with a little human finishing at the end.
The other advantage I like with CNC is the variety of materials I can work with, it can be plastic, printed circuit boards, wood, and even metal. There are sites out there with patterns to be used with a benchtop CNC or you can just make your own 2D drawings and import them into the CNC software. Everything I have used so far is open source, so the only money I have spent has been on the hardware, not the software.
Finally, there is an upgrade path with my little CNC. If I want to upgrade the spindle motor, I can, and work with harder materials. You can even swap out the spindle motor for a laser cutter. When researching which CNC to buy, the next tier up is over $1,000, and I can order a lot of boards for that kind of money.
For now, I will enjoy playing with my little CNC, coming up with custom controller housings and maybe some fun art as well. On top of that, I am learning gcode and how to control a CNC, and maybe I will upgrade way down the line.
In world at war, something much closer to home has happened. On Monday, March 11, 2022 everything changed for me. For the first time in my life, after 25 of engineering, I was laid off. At later date, I will detail who I was working for, once the severance check goes through and I have a new position. I worked at company X for 7 years as a Design Test Engineer, an interesting title for a job that, quite honestly, got really boring at the end. From here on out, this is will a cautionary tale for anyone who wants to try Scrum.
Before I detail what the heck scrum is, I want to preface that when I started working at company X, scrum was just starting to be used in the east coast facility, and not back here in Illinois. I enjoyed what I was doing and was almost done with a complete set of code for a new test site, then Scrum started. As a spoiler, Scrum was originally meant for software programming, not hardware. Sadly, 90% of what company X made was hardware with a software component. It does not work well, if at all, or worst case, as I saw, actually slows down hardware development to an absolute crawl or even backwards. Scrum does not work. It hides the failings of bad or mediocre engineers and pulls down good or great engineers.
Scrum is based on the book SCRUM The Are of Doing Twice the Work in Half the Time, or I like to call it, the book of lies, from Jeff Sutherland. The ‘old’ way of doing things is the waterfall, when all the steps are planned out, with dates and milestones. It is not a perfect system, but in my opinion, it still works for HARDWARE based development. A modified waterfall with some agility built in to deal with setbacks has been the best compromise. I am sure some version of Scrum/Agile could work, but you really need to have it across the company. The biggest fault I have with of the book is the vilification of task switching along with the underestimating the impact non-value task that the rituals of Scrum.
From the very beginning of the Scrum switchover at company X my biggest concerns were the time to be used for the rituals and lack of true cross functional teams. Let me tackle them one by one:
Rituals and the Time used:
-Daily Stand up -15 minutes a day, ideally. In reality, depending on the size of the team and globs onto the team, this could be as long at 30 minutes. You are supposed to state what you worked on, what you will be working on, and if there is anything in the way. In reality, the sales guy chimes in how angry the customer is, the product owner, which echos the same and outside work that may be needed, and production…and quality. Instead of a nice, tight 7 person team, you end up with a 15+ person standup.
-Demo preparation -Up to an hour meeting + time it takes to produce pointless power power slides, which took me 2 hours or so per ‘sprint’.
-Demonstration – Usually an hour to 1.5 hours.
-Retrospective – Was somewhat quick at 30 minutes.
-Sprint planning – 30 minutes to an hour.
A ‘sprint’ is a 2 week period of work where we tracked information on a Jira board. Lets add up all the time spent on this: Lets be generous:
20 minutes per stand up x 10 = 200 minutes
Demo Preparation 180 minutes
Demonstration 90 minutes
Retrospective 30 minutes
Sprint Planning 30 minutes
530 minutes, 8.883 hours per two week sprint. So, we more or less wasted over an entire day PER PERSON for 80 hours. That’s about 11% of our time spent doing. Meetings, planning, demos, retrospective. How is this really an improvement over the typical way of doing things? In addition, this ignores the task switching time that is supposed to be the problem with waterfall management. Even this loss of time is nothing compared to the total stall of progress I experienced. In the software world, if there is an issue, you can just throw out the code, re-write, test, and release, all in the span of 2 weeks. This is just not possible with hardware. You have to order components from external suppliers. If the design is wrong, you have to re-spin, retest, and try again. This takes weeks and weeks, months or more. You can’t just fix a few lines of code. With all the delays, the tasks just keep getting kicked into the ‘backlog’. The can just keeps getting kicked down the road. This is supposed to be impossible in scrum, but in the real world, this is not the case. The Scrum book is deceptive in a major way, summed up in a diagram.
Did you notice anything odd with this diagram? The only reason the Scrum team is faster is the boxes are smaller. In the real world, the boxes are small, but you end up with MANY more small boxes and if the task does not get complete, it had to spill over into the next sprint. The task does not get done because of the very nature of the speed of hardware development. This problem was further exacerbated in company X by repeated, intermittent failures and test cycled that could take days or even weeks to see if a change worked. Even if everything worked perfectly, the text process took close to 2 weeks to complete. You can see here what I experienced with Scrum. The original diagram also does split up the tasks into the 2 week sprints, with all the associated overhead, but does not duplicate any sprints or backtrack.
To expand my real world experience, there were 3 cable assemblies, each different, that got mated to another assembly, not interchangeable, that got mated to yet another larger system, so lets call them A, B, and C. What I ended up with A1, design the cable, 1 sprint, have external vendor make the cables, 3 to 4 sprints, 6 to 8 weeks, receive cables, test, Sprint 5. Find the cables don’t work, go back to Step A1, another sprint 7, send back to cable vendor, sprint 8,9, and 10, receive back, test, Sprint 11, initial test so we integrated in to B. Attach to B in task B1, Sprint 12, then test, Sprint 13, find there is a issue, go all the way back to A1, redesign able, Sprint 14, get new ones from vendor, sprint 15, 16, 17, skip to B1, test again, B2, Sprint 18, find it fails again…this repeated for almost a year. For three cable assemblies. It was insane, and this was just part of the whole, and you can imagine the rest was not much better. Repeat this for 5 years.
At the end of the day, the project X was no closer to being complete than it was 5 YEARS before and I am out of a job, along with Mr. M, who founded company X, was outed, sorry, retired at the same time.
From my perspective I think this is what happened: Mr. M was told about Scrum and how it was the best thing since sliced bread. He directed a SOFTWARE team to work using Scrum and it worked well, since it was software. Around five and a half years ago, Scrum was rolled out over company X. I remember having to read the book, then even been flown out to New England to learn more about Scrum. Looking back at the financial records of company X, the very same fiscal year they went from a somewhat profitable company to losing money. Over the last 6 years, company X has lost an average of $10,000,000 a year and close to $60 million total. The whole scrum process is a fiasco. This problem was not limited to the team I was on, but also with a research and development scrum team that has produced no working product despite millions of dollars of equipment purchased and external contracts. In the end, an external investment firm must of taken a close look at the finances and realized company X could be turned around and elected a new board of directors, which then removed the Mr. X and downsized the company around 10%. I was in the 10%. I know why they did it, I am still angry and disappointed, but it had to be done. If they really want to turn around company X, they need to end scrum and end it now.
Why did I write this long ass blog post? I wanted to get everything down before it fades in my memory. My prediction for company X is either they will sell the intellectual property rights to a competitor or sell the division to another company or possibly spin it of as its own company.