Wednesday, August 20, 2025
AI: More Luck Than Science?
Tuesday, August 19, 2025
Gaining Experience by Fixing Existing Web Apps
Here’s a little secret: most small business web apps… kinda suck. Small businesses usually don’t have the budget for high-quality software engineering, so their apps are often missing important features, are slow, outdated, and not mobile-friendly. But that’s actually an opportunity for you as a student. Instead of building yet another “hello world” project or a to-do list app no one uses, try this:
- Find a small business with a clunky website or app, e.g. diyetta.
- Use it on PC and mobile, make a list of improvements.
- Make a copy of the whole app or parts of it and make it faster, cleaner, easier to use.
- Demo your version to the owner.
Worst case? You get real-world experience. Best case? You get paid. Either way, you win. You’re not just learning to code—you’re learning how to:
- Create real value (solving actual problems, not just coding puzzles)
- Sell your ideas (convincing skills)
This one simple strategy can turn you from “just another student” into someone who can point to real impact. That looks so much better on your resume than “I built a weather app.”
So… what’s the worst small business web app you’ve seen lately? Maybe that’s your next project.
Tuesday, June 3, 2025
Startup Checklist for Students
Thinking about turning your hobby or project into a business? Ask yourself:
- Who wants it? What makes it better than the alternatives?
- How will people hear about it? A great product is useless if no one knows it exists.
- How will it make money?
Friday, April 4, 2025
Teknofest Fighter UAV Competition
I am helping an undergraduate team with their Teknofest Fighter UAV Competition. The most difficult technical challenge is autonomously detecting and following other fixed-wing UAVs in the air. Teams must use a single stationary camera—no gimbals are allowed [Specification 6.1].
My first piece of advice to the team was to set realistic expectations and define intermediate success metrics, so that regardless of the final outcome, they can feel good about their progress. Last year's winning team was established in 2017 and reused a UAV they had been improving since 2020, which shows that having a realistic chance of winning requires several years of preparation.The domains in which you need to be knowledgeable include:
- Image processing, object tracking
- Airplane aerodynamics
- Mechanics
- Guidance and navigation for autonomous take-off, flight, waypoint navigation, target tracking, landing
- Embedded software development for UAV avionics, real-time operating systems
- Ground station software development
- Telecommunications for telemetry and commands from ground station
- System identification
- Manufacturing and system integration
- Use of simulation tools (e.g., ArduPilot SITL, Gazebo, QGroundControl)
- Public relations and marketing to acquire necessary resources (~$5,000)
- Ground testing of individual components and the integrated system
- Manual flight of the UAV for system identification maneuvers
- Autonomous UAV flight testing
Mastering all of these domains is beyond the capability of any undergraduate team. Fortunately, systems like Pixhawk Cube Orange and PX4 Autopilot handle autonomous flight, NVIDIA Jetson series can handle object detection, and ready-made airframes like the X-UAV Talon reduce the production burden. This allows the team to focus on UAV-ground communications, tracking the target UAV in the video feed and generating appropriate guidance commands for their own UAV to follow it.
In light of all the above, here are my suggested success metrics:
- Pass the Technical Qualification Form
- Learn how to use ArduPilot SITL with Gazebo
- Pass the Critical Design Report
- Obtain monetary/component sponsorship
- Ground test all components
- Submit System Identification and Flight Evidence Video
- Qualify as a finalist
- Participate in the competition and complete at least one mission
- Win a prize in the competition
- Win first place
Sunday, March 23, 2025
Memory and Storage Latency
Below you can see memory and storage latencies and their corresponding analogies. For example, a cache miss that triggers a memory access from RAM, is about 100 times slower than the L1 cache. A skilled engineer can make an app run at supersonic speed instead of at a snail's pace — often the difference between a popular app and a dead one.
Component |
Latency |
Order |
Metaphorical Speed |
|
CPU Register |
~0.5 ns |
1 |
๐ 3,600 km/h Supersonic jet |
|
L1 Cache |
~1 ns |
1 |
✈️ 1,800 km/h Commercial jet |
|
L2/L3 Cache |
~ 5 ns |
10 |
๐ 360 km/h High speed train |
|
RAM (DRAM) |
~100 ns |
100 |
๐ต 18 km/h Scooter |
|
Flash (NOR) |
~10 ยตs |
10⁴ |
๐ข 0.18 km/h Tortoise |
|
NVMe SSD |
~50 ยตs |
10⁵ |
๐ 0.036 km/h Snail |
|
Wednesday, March 19, 2025
Minor, double major or projects
Engineering students often ask, 'Would doing a minor or double major benefit my career?' My answer is that pursuing a minor or double major is a demanding process. Instead, by working on projects related to your field of study, you can achieve much greater benefits with less effort.
Wednesday, December 18, 2024
Why I unit test
I primarily write unit tests for the following reasons:
- When I write an algorithm, I almost always miss some edge cases. Writing unit tests helps uncover most of them.
- Unit testing forces me to maintain clean function interfaces and design modularly.