From time to time, I dabble in some photoshop work. The results are some fun, unique alters of existing Magic cards. Enjoy!
For a weekend project I built a backlight array for my TV which gives off ambient lighting according to what colors are being shown across the edges of the screen. Powered by a microduino and Abalight software for Mac.
According to the experts, backlights offset the brightness of the screen by lighting up the entire wall, while also giving the impression that the movie is bigger than just the screen. I just say “woot.”
Over the last 4 years, 2 of which as a manager, I collected notes about what I and others thought were the marks of a great engineer. I’ve compiled this list to inspire other engineers and also give solid examples of each trait. I’m sure there are many more things that can be added to this list, but its a start.
Finds problems, makes good decisions and escalates if unsure of correct path.
“This was broken, so I fixed it”
“This is broken. I see 3 possible solutions…”
Communicates clearly on technical topics to peers and managers. Asks good technical questions.
“Here are the 3 things we are working on and how they fit in the larger picture”
“Why is X the correct solution? What are other options?”
Shares what they learn via blog, tech talks, etc. (Helps you become more articulate and grow by getting challenging feedback)
“Lately I’ve been reading about…”
“Have you ever wondered why…”
“This is amazing and I had to share …”
Writes clean, modular, testable code, paying attention to detail.
“I’ve thought through these different solutions, but chose X because…”
Brings focus and vision to projects, taking into account the bigger picture and knowing what to trade off.
“We can start with X and iterate till Y.”
“Z is interesting, but not neccessary.”
“I think there is a bigger opportunity here if we do X as well”
Successfully delivers task/bug/projects to completion and cleanly hands off. Doesn’t let things drop!
“I wanted to check back in with you on X.”
“Do you have everything you need to move Y forward?”
Able to lead a project, create a roadmap and inspire team members.
“Based on the ask here, we need another experienced person to help with X.”
“Here is the plan for the next few sprints of this project. Thoughts?”
“I think this can be better by …”
Prototypes to get real data and answers when unknowns arise.
“I wasn’t sure about X, so I did an initial prototype and found…”
“I prototyped two possible options with this resulting data. Based on the data, I think option A is the best choice.”
Takes initiative, steps up.
“I’d like to learn more about X”
“I’d like to drive/lead X”
“Y has been bothering me and I’d like to make it better”
“I think there is a huge opportunity here if we spend time doing Z”
Is a standard bearer of the culture (collaborative, helpful, driven, insightful, friendly).
“What can I help you with?”
“Was that clearly explained?”
“Anything else I can do to help?”
“I noticed X and think Y could really save some time.”
I recently had an issue with a server hosted at OVH.com. One Saturday, it completely failed to boot and there was no SSH access. After a little pleading with OVH to fix the server(since I had no access) , I was flatly told “No” several times. This was a dedicated server and as such, I was responsible for all aspects of its software. “But your physical disks are failing to mount!” No help. Grrr, ok I can solve this.
Here’s the only problem, I don’t even know what the error is on boot! I can’t see any of the boot screen, so I don’t know where its failing.
OVH has a convenient feature know as Rescue Mode which allows you to boot to an alternative OS, so you can mount and correct any issues on the primary drive. Utilizing this feature I got access to the disks and RAID array. Everything seemed fine, but I ran through all the checks to be sure.
- Hard Disks – No errors
- Raid Array – Needed to be resynced, but does not fix boot
- FileSystem – OK
- Boot Logs – No help
- Partitions – Disks are out of order, but does not fix boot
At this point, I’m out of ideas, so I call OVH one more time and ask them to look at the boot screen and tell me where its stuck. They agree and tell me it boots to GRUB> prompt and stops. Ok, this is good information.
I log back into rescue and scour the internet for a way to fix this. The answer is found in an obscure ubuntu forum, which perfectly describes a way to reset the grub loader on each disk in the array, when utilizing a rescue mode.
$ sudo fdisk -l (From this you need to find the device name of your physical drive that won't boot, something like “/dev/sdxy″ - where x is the drive and y is the root partition. Since I was using a software RAID, root (/) was on md1)
$ sudo mount /dev/sdxy /mnt (Mount the root partition)
$ sudo mount --bind /dev /mnt/dev
$ sudo mount --bind /proc /mnt/proc
$ sudo mount --bind /sys /mnt/sys
$ sudo chroot /mnt (This will change the root of executables to your your drive that won't boot)
$ grub-mkconfig -o /boot/grub/grub.cfg (insure that there are NO error messages)
$ grub-install /dev/sdx (NOTE that this is the drive and not the partition. try grub-install --recheck /dev/sdxy if it fails)
Ctrl+D (to exit out of chroot)
$ sudo umount /mnt/dev
$ sudo umount /mnt/proc
$ sudo umount /mnt/sys
$ sudo umount /mnt
Hopefully this will save someone some agony in the future and give you a few hours of your life back.
He who embraces his fears and moves in any direction, will learn from his mistakes and move forward. He who simply acknowledges his fears, will never succeed or fail. Rather he will be left standing still, straining in vain for peace.
– Tony C
The Dalai Lama, when asked what surprised him most about humanity, answered:
“Man…. Because he sacrifices his health in order to make money.
Then he sacrifices money to recuperate his health.
And then he is so anxious about the future that he does not enjoy the present.
The result being that he does not live in the present or the future; he lives as if he is never going to die, and then dies having never really lived.”
I had been wearing a demo Apple Watch Sport for a few days, when I noticed a few scratches on the screen. Damn, I thought. It had only been a few days and I hadn’t bumped or scraped it on anything significant. In addition, I had been cleaning it with a microfiber cloth, so I was sure it hadn’t been from that. But it was still odd considering how long I’ve had an iPhone 6 with no cover and 0 scratches. So I did a little digging.
Sure enough there are a few threads on Apple’s own website detailing how common, everyday usage is resulting in scratches. Disappointing, but maybe people are simply being careless. However, for some non-transparent reason Apple has also quietly updated their product text removing all mention of being scratch resistant.
Rolling back 2 weeks on Apple’s own product page for the watch, we see the following text. Notice the phrase, “especially resistant to scratches and impact.”
But if you look at the current version of the product page, you’ll see this text.
Apple removed front page, product messaging referencing its watch being scratch proof.
Here’s my recent talk entitled “Chasing 60fps, Using ReactJs to Rebuild Netflix.com.” We discuss both the advantages and challenges of building with ReactJS for the new Netflix UI.