adamcrow64

frontend broke first. Too many different styles and frontend personalities. When you bring new people in, they bring with them very different ways of designing and building things. Backend devs and devops were fine. But frontend had new technologies, different architectures etc . It was very difficult to get new frontend devs to adhere to the system architecture because they were more superficial in their design and not as CS trained.

exactly

We moved to garage because minio let us down.

We moved to Garage. Minio let us down.

Back in the early 90s I created a mosquito repeller page. Based upon the electronic mosquito repeller kits that emitted a frequency.

Back in the early 90s I created a mosquito repeller web page

A classic that seem to be lesser known... --> darthsim/imgproxy. (docker) , this is an image proxy. easily run under docker then you can fetch any web image through it and be able to resize on the fly and cache! Fantastic for auto creating user thumbnails etc and not needing to generate different size images. Thanks to the author (Sergey "DarthSim " Alexandrovich)

I've cofounded a number of startups. I have found that a major rule is that you should NEVER let a non technical person lead a technical startup. They simply don't get it. It is way easier for the tech person to be the CEO/CTO and partner with a CMO/CFO who will get their hands dirty. There is a good reason that accountancy/legal,consulting firms are run by accountant thinkers and the big tech companies run by tech thinkers. I understand that the skill most represented in the fortune 500 CEO is technical.

So if you are looking for a tech cofounder you should look for them to be CEO.

I like to know that candidates can recall their study. For engineers, one of the biggest mathematical learnings in their degree is the study and use of imaginary numbers. In Australia this is taught in year 11/12 and is taught to kids who show aptitude towards STEM. Identifying these early adopters has worked well for us. So the go to question that we use a lot is "What is the square root of minus one?".

This culls a lot of non mathematical people. (And we find that Mathematical people generally make for better STEM employees in a tech setting).

If they answer correctly (and many who get through the initial resume culling process do) then we follow up with a second question that is not important to answer but will show a candidates sense of curiousity (super important).

What is the answer to the first question to the power of the answer to the first question?

Fascinating answer to this second question that can delight the candidates we are after.

Flutter. It gets the job done.

I used a genetic algorithm back in 1993 to calibrate a commercial 3D freight laser scanner. The problem we had was that the triangulation equations for the laser angle, camera pixel map, and distance between the camera and the laser axis were very difficult to solve using standard equation solving. In the end we created a calibration 'box' that we scanned. Without ANY hints our genetic algorithm found an optimal calibration set within 45 generations. Fantastic!

Just a comment. You have to expect that at some point you may become invalid or disabled to some degree. Although you may not need stuff now, make sure you keep a set of reading glasses or short sight glasses. A walking cane. Look after your teeth! Flossing equipment. Lots of toothbrushes. Tonnes of suncream.

I notice that big tech companies are run by people who are technical. This allows you to talk to them far more efficiently. If I recall, the most common professional background of CEOs in the fortune 500 is Engineering

(1) Highlight a code of professional ethics (e.g. IEEE) (2) Internal lecture sessions (like twunde advises) (3) Engineering is about application of systematic thinking to issues. Highlight measurements, automation, professional conduct, and cost management. (4) lead by example.

Take a picture of the outside. use the raspberry pi to project it onto the wall. Also you can use the raspberry pi to project various bit patterns onto 3D surfaces and then by identifying the 3D pixels you can capture 3D surfaces.

A Plethera might be a better one.

We're a startup here in Australia and we use Java extensively. It has been trickier to use than PHP but the extra effort has allowed us to produce a very sophisticated system.