Hacker Newsnew | past | comments | ask | show | jobs | submit | m-a-r-c-e-l's commentslogin

3 days? Do it!

It took our team 5 man-years (1 year of time) to upgrade from Laravel 4 to 5...


PHP is super-fast today. I've built 2 customer facing web products with PHP which made each a million dollar business. And they were very fast!

https://dev.to/dehemi_fabio/why-php-is-still-worth-learning-...


At the risk of sounding out the obvious. PHP is limited to single threaded processes and has garbage collection. It's certainly not the fastest language one could use for handling multiple concurrent jobs.


That's incorrect. PHP has concurrency included.

On the other hand, in 99.99% of web applications you do not need self baked concurrency. Instead use a queue system which handles this. I've used this with 20 million background jobs per day without hassles, it scales very well horizontally und vertically.


They didn’t say it was the fastest. Just that the language per se is fast enough.


> the language per se is fast enough

I literally explained why this is not the case.

And Nextcloud being slow in general is not a new complaint from users.


I'm still coding like it's 2001!


For me it's the opposite: if your job is your passion, it doesn't feel like a job anymore!


May I ask approximately how old you are and what field you're working in? (Or, being passionate in?)

I feel like this is not a realistic view to sustain in most modern tech environments, unless you love inefficiently producing ineffective solutions that just so happens to be profitable, or you job hop every 1 - 2 years.


47 now

First company with 23, sold with 33.

Second + third company founded with 36, sold at 46.

I was the software engineer in the founders team, built alot by myself, even in the last years with a tech department of 30 people.

After doing nothing for 1.5 years, I am back with a new startup, being the only developer. Because I love it, and I am good at it!

It's my passion...


Interesting, thanks! I feel like that kind of confirms my position: you're not someone who has the same passion for coding, you have a stronger passion for building, leading and selling tech companies, which is why you've done that multiple times.

I've never been a founding engineer, but typically a direct report to founding engineers.

The people I worked with in your position were either like you (e.g. enjoyed programming but clearly got a big rush from the business and money side too) or they were genuinely just pure passionate programmers and miserable, as their role takes them away from that.


One option is to become a freelancer, there you usually get a new project every 6-18 months in my experience.


There's a whole categories of skills, abilities and problems that are never confronted if a person changes job every <2 years.

Hot take: what if the rise in enshittification and crap tech is because good tech can only be produced with the hindsight of a stable tech career from a stable tech employer?


That's a different topic though. This was about passion in coding for living.

I don't think it's the employee's responsibility to stay in one company if the stability and in-house career path options are questionable, as usually is the case.


If your job is your passion, and your downstream customers give you freedom to treat it as such, it can be fun.

The fun gets sucked right out of it when you have people breathing down your neck waiting for your output, are very particular about what they expect from it in a way that doesn't align with your creative values, etc.

Not all of us have a Lord Saatchi willing to bankroll whatever our brains fart out and call the result brilliant (likely to pump up its value to buyers). Matter of fact, that may just be what ZIRP-era VC can be conceptualized as: business model "Uber for Lord Saatchi-style patronage in tech".


Love 4 htmx


correct



I did something similar 20 years ago. Setup 4 Nokia phones with 4 SIM cards for the 4 different networks in Germany.

It was possible to connect them via a serial cable to a linux machine and receive/send SMS.

Used that to offer a horse betting service: people could bet on horses via complex SMS syntax. It worked, but never made enough money :)


wow, super hard game...


Did you try it with mobile or desktop? It is primarily intended to be played with mouse. I might try to make it easier to play on mobile at some point.


There were a lot of commercial hole punchers at that time. See here for some photos e.g.

https://www.forum64.de/index.php?thread/38406-diskettenloche...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: