dejv

Most other breeders use pen and paper and they are fine, but hey I am programmer and I am going to write software.

Thanks to cultivation dificulties as well as bad image from previous times (thanks to big yields it use to be used for poducing cheap table wines) make this varietal slowly dying: old blocks are being replanted by other varietals.

I think it is a pitty as St. Laurent wine is very interesting and quite memorable. Luckily I've bought few blocks with old vines and I am selecting plants with loose bunches and am trying to create new clone with more favorable growing characteristic.

I guess it is all about positioning, there is no way to win trying to compete in budget low quality work (fixing small business websites, writing scrapers and whatever is trending on upwork these days) and hoping to climb ladder somehow.

I went through subcontracting for digital agency I've met through some of my open source work.

At the end I've made nice money, bought a house and hit glass ceiling few times. It was fun, but then kids happened and time zones together with work pace required to sustain senior roles in startups just make me quit and don't look for another opportunity.

App for practicing some basic piano stuff, things like note sight reading and piano scales. Worsk best when you connect MIDI keyboard. (More exercises comming soon)

Drones for spraying is buzzword for past few years, but it isn't going to work for many different reasons both technical and legislative. At the end the act of spraying is not pain point for vineyards: the current technology is dependable, easy and proven. (Speaking as a certified farmer)

Biggest failure was SAAS for organizing wineries and generating reports for carious government bodies. There are various old software from 90s that do that or you can use paper books (depending on country you are not allowed to use excel).

I've spent around 3 years of fulltime work but it turned out farmers do not care about software. They might use some old desktop software or just hope that inspection is not going to come. Software is still up and running and there are some paying customers, but it just doesn't make sense to spend much time working against the wind. Also my addressable market is not big enough to support additional development.

Here is a map I found: https://en.eurovelo.com/ev9 This route actually didn't end at Venice as it suppose to end (and didn't pass through the Baltic states), but it is nice overview.

Huge companies have many advantages in certain production areas, but there are many others like intensive vegetable production, wine grapes, poultry, rabbits (just to name some animal production) and some speciality crops that favor small producers. Farms just need to invest in building their own supply chain.

I am pessimistic about having heavy duty industrial scale tractors with current battery technology. Those machines are monsters and when you interpolate consumption from light workloads to those monsters it just doesn't compute. Another angle in economics is that those machines have to work for many hours a day (combines in heavy seasons run for 12+, 7 days a week) which is also hard with current batteries.

What you can see a lot on current market are "heirloom" varietals made by entrepreneurs that take industrial variatel, cross them to create new completely new varietals. But just because something doesn't look like modern tomato it doesn't mean it taste good.

You can still find old varietals in seed banks and around seed savers, but hip breeders are much more noisy in the market. I am not saying those new breeds are worthless, but they are kinda hit and miss and I would not consider them heirloom.

Decision is usually by customer, I am trying to go with having man-days as billable unit as much as possible, but it is not battle worth winning every time. At the end what customer want is having clear idea how much is project going cost and trust that quality would be (at least) good enough.

I would stay away trying to be super detailed about what you did in small time increments, unless required by customer. Nobody really cares about it, it is much better to say "Feature A development. 30hrs" than "Feature A research 15 mins, Emails 1hr. Rework screen A 4hrs... and so forth in long letter that looks like AWS bill.

I do track my time per project (usually break down to dev and admin category) but give out just half-day or maybe hour increments.

Almost anything for industrial use cost you a leg and then some. If you want to experiment with CV at home I would take a look at that high quality camera module from RPi.

Industrial and industrial IoT is one of the use case for these kind of boards. These machines are not produced in high quantities so finding existing modules saves a tons of R&D budget.