- kugelblitz parentAs German ex-football (soccer) coach Sepp Herberger would say "Nach dem Spiel ist vor dem Spiel" (After the game is before the game).
- Had the same problem while trying to decide which Roborock device to get. There's the S series, Saros series, Q Series and the Qrevo. And from the Qrevo, there's Qrevo Curv, Edge, Slim, Master, MaxV, Plus, Pro, S and without anything. The S Series had S8, S8+, S8 Pro Ultra, S8 Max Ultra, S8 MaxV Ultra. It was so confusing.
- Solo Dev on my own PHP project since 14 years.
I wait 1-3 months, but then update. It used to take way longer, because Amazon's Elastic Beanstalk platform would take longer to update, but I've now changed to Platform.sh and the transition should be easier.
It has been very backward-compatible (i.e. stuff that works in 8.n also works in 8.n+1; and unless you use exotic functions or are relying on special functionality, it should work for you, too).
Once I'm at 8.4, I would slowly update the code / syntax with rector and the assistance of phpstan.
For framework updates I wait 1-2 patch versions before updating, because of composer dependency problems and sometimes bugs do still find themselves into new releases (e.g. I would wait at least until Symfony 7.2.1 before upgrading from Symfony 7.1.x).
- I use Symfony (PHP based framework) and it works fine. I've been able to get into Django (Python), Laravel (PHP), Java (Spring) and even Grails (Groovy) because they either had similar concepts or even similar syntax (I mostly do web development, so this is a very biased take).
Being a freelancer, I need to focus on what's marketable. Sure, Elixir will get me into a niche, but I will have way less projects to choose from. And when I start a project for a company, if I start with Elixir, I will also have a smaller pool of devs to recruit from. It's a chicken-and-egg problem.
Nowadays, if I start a project, I would try to build on monolith and full framework with a PaaS.
Unfortunately, most projects want to start out "the right way", which means separate backend (e.g. Java), separate frontend (React), rented server (e.g. Hetzner server) and custom deployment (some pipeline an outside agency built when they first started the project).
I'd rather spend 400 USD on tools each month, but then only need 1-2 full stack devs instead of 6-8 people (1 sys admin, 1-2 deployment, 2 backend, 2 frontend) and with all the overhead that comes with it.
- That's true :D, thanks for the correction!
I think I was still in German mode, it's called "electric punch" (Stromschlag) if translated literally, my brain went the easy route and tried to find the closest match.
- I have another, different oddity. Whenever my colleague and I stand up (or also sit down?) on the desk, his Dell monitor would turn black for a few seconds. I don't remember the specifics, but I think it was mostly just the two of us, when other people say down if was fine.
Even if he's sitting on a different table, the moment I sit down his screen would blank for a few seconds then continue to work normally.
I also get electrocuted easily when I use the escalator. It almost doesn't matter what I wear, so it might have to do with my skin or it's conductivity? But that's just a wild theory that would need to be checked.
Edit: Some research seems to point to the static electricity from the chairs.
- Well, one can exist on HN.
- I once did that for a client of mine.
I took the WordPress-based / WooCommerce system and split it into 1) the Shopify system for admin stuff and also the whole payment system and 2) the "frontend" i.e. the consumer facing part BEFORE the payment (I used Symfony, similar to Laravel, but more modular and I was more familiar with it). Theoretically you could fetch all the product data via the Shopify API and then sync it automagically. But in the first iteration, we just copied some of the basic product data into a simple Symfony Admin backend and made a simple javascript-based checkout slide-out, and only when they were ready to pay, they would be forwarded to Shopify.
This way we would have full control of the user experience up to the point of purchase, and then Shopify would take over. I thought this was the best way I can deliver a performant website, while also being able to sleep well, because all the money stuff and all the customer data is handled by Shopify.
I was able to increase search engine traffic by 30% this way, reduce page size and increase page speeds and revenue increased significantly.
After 3 years, he decided he wanted to make it more "professional", so he fired me, I got none of the credit ("the search engine traffic must be because of better branding - and the page isn't up to my standards of aesthetics... yes, the designers who were supposed to deliver the designs kept stalling and delivered NOTHING and you had to just create something on the fly before the main selling season, and yes we had huge sales gains on the website and more traffic, but this was not because of the website"... they didn't change any of the marketing or any of their strategies, by the way.) So they hired an agency team with a project manager, designer, developer, marketing person; who then asked me to give them the source code from git so they can upload the code to their FTP server (!).
And they pretty much didn't change anything for a few years, everything looked the same. After like 4-5 years, they adjusted the design a bit, but still looked VERY similar.
- It's a different ecosystem than Wordpress.
I'm having some trouble finding analogies.
But maybe Symfony would be something like Linux Debian, has all the building blocks, it's modern but stable and well documented. Laravel is like Linux Ubuntu, it bases many things on Debian, but adds many things to make stuff a bit easier for the user. It's "shinier" and it has better marketing. You can add Debian stuff to Ubuntu, but you can't necessarily add Ubuntu stuff to Debian.
Symfony is more modular, you can add the components to any PHP project. Whereas Laravel uses many Symfony components and adds some syntactic sugar, but once you go into Laravel, it's difficult to stray away too far from the "Laravel way". Laravel uses many Symfony components, but Symfony can't easily use Laravel components.
Self-hosted Wordpress would maybe be comparable to a rooted Android phone. It has a very specific use case (for Wordpress it's fundamentally a Content Management System). You can add all sorts of plugins and additions. But it's also easy to accidentally break something. And once you added too many things, it might be difficult to update without breaking many things.
In the end, they're all Linux based, but living in very different ecosystems (just as Symfony, Laravel and Wordpress are PHP-based).
In programming terms, Symfony might be similar to Django (Python) or Spring Boot (Java), whereas Laravel is "cousins" with Ruby on Rails.
- I think it's more that it's a crap job market. Have been dev freelancing for about 10 years, used to be able to choose from a few projects within a couple of weeks of searching.
But the last 18 months have been hard. On some freelancing projects I was up against 80 or 120 other devs. (I live in Germany.)
Recruiting agencies have told me the same. I finally found 2 part-time projects after 6 months of search and will now try to wait our the dry period.
- For my 12 year side project, I recently moved from Elastic Beanstalk after 6-7 years to Platform.sh, because "it just works" even more so and it was way easier to debug (EB just says "error in step 18_install_yarn" or something).
I use Symfony (Php) and have not used a full SPA after I retired AngularJS (v1) like 10 years ago. What people now call server side rendering (SSR) is just how Symfony works with its regular Twig templating language (heavily inspired by Django's templating language).
As I gained more experience, I rewrote it. Once from vanilla PHP to Laravel, then later to Symfony.
- I would argue adding JavaScript on top of Laravel will make you slower. You can use Blade as the templating engine (or how JS people would call "Server Side Rendering" but which has been default for most full stack frameworks). Otherwise you need to create 2 additional interfaces, one for backend and one for frontend. And an additional layer of error handling.
I personally prefer Symfony over Laravel because of it's modularity and extensibility, but Laravel has the edge on getting started quickly and available SaaS features (such as billing modules and stuff).
If you need SPA-ish features, you could use htmx and if you need some on-site interactivity, I like Alpine.js.
- Just use fastmail and set the DNS to theirs, they should handle the rest. I also like that they have catchalls, i.e. I can post hackernews@mydomain.com or stepstone.com.engjobs@mydomain.com to figure out how people found out about the email address.
Pros: You can always change the provider in case you change your mind in the future. With gmail, you're locked in to their service (and if they lock you out for some reason, well, you're stuck).
- How about going freelance contracting / consulting? They will probably appreciate your experience as CTO and also your understanding of how to push a product forward.
I've only had side-projects, but one of them was big enough to pay the bills during the best of times. Currently it has hit a speed bump (more visitors, but less orders) so I'm just running it passively on the side, generating a little bit of profit, while I do freelancing.
- Is it a company email which they control now? Maybe that's how they changed it.
- Shoot, I'm just realizing that we're as far from 2038 as we are from 2010.
In 2010 the the iPad was released and the movie Avatar had come out. So we're closer to 2038 than the release of the iPhone (2007).
- Security in vanilla php using old tools is a headache.
I use Symfony and using the form component (https://symfony.com/doc/current/components/form.html) you can achieve much of what is needed.
If you use the framework as well (which is very modular nowadays) you also have security built-in (https://symfony.com/doc/current/forms.html).
But probably not as fast as a "quick and loose" approach if you don't know Symfony yet, but extendible and secure (if you do know Symfony, it might be faster than the vanilla php approach, because you can avoid much of the "generic" code, the validators, the error handling, avoid SQL and XSS injection).
- > This could be a once-in-a-lifetime viewing opportunity as the nova ouburst [sic] only occurs about every 80 years.
- I suppose hiring an SEO agency to do marketing is like hiring a painter to remodel a house to sell it.
You sort of already decided what you want to focus on. But maybe the remodeling needs other things first, e.g. someone to clear out the stuff to clear the pathways, add new furniture, redo some of the floors, redo the tiles in the bathroom.
Same with the site, maybe you need someone to optimize the web site performance, maybe you need to create a funnel and several landing pages, maybe more marketing in LinkedIn groups.
SEO is important, but it should be part of a holistic approach towards marketing.
And if it looks spammy to you, it most likely is. I'd stop the cooperation immediately to prevent further reputational damage. Don't just check page views, but also if people are staying longer, clocking through the site, ordering anything, etc.
- AI Overlords for 400, please.
- I feel like 95 is more difficult now than 2 or 4 years ago.
- I've never heard of Linear. Most of the companies I Work with use JIRA. Small agency to medium sized E-Commerce. (Germany based.)
- PHP / Symfony.
It has Auth, Templating, ORM, Email, Caching, Forms, Validations.
For frontend I like Bootstrap or Tailwind as a base, but for interactivity I use a combination of htmx and Alpine.js, so everything's pretty light-weight.
In the frontend world, I started reducing my reliance on it. I started quite a while ago and had went through jQuery, jQuery UI, bower, gulp, grunt, AngularJS, then the completely rewritten Angular 2+, Vue.js, npm, yarn 1, yarn 2, yarn 3, webpack, rollup, Parcel.js (which I like)...
It was too much for me to keep up. So I stuck with Symfony and try to keep the frontend light-weight.
- By now I'm quite efficient, haha.
Heavy stuff in the beginning, fragile stuff at the back, from large to small (so that I bag the heavy and large stuff in the bottom and then fragile and small I squeeze in carefully).
I recently heard of a tip from people who become anxious at the cashiers: Fruits and veggies at the end, because often they need to weigh it and sometime also input numbers manually, this gives those extra few seconds at the end.
- Oof, 4.5 MB for a decorative image.
- In Germany you always bag everything yourself and in the discount stores you have 1.4 seconds per item to pack stuff while the cashier is sliding stuff towards an area of maybe 60cm x 100cm (2 feet by 3 feet) where if you bag it too slow you'll hold up the line and people will look at you.
- I also still use Bootstrap. After adjusting it via the .scss files, it looks custom. Tailwind keeps popping up on my radar, but Bootstrap's utility classes are good enough for now.
I even exchanged the bit of Vue.js functionality with htmx.
And I use a bit of Alpine.js and vanilla JavaScript here and there, but it's very minimal.
- Yeah, as a full-stack / backend developer using PHP / Symfony (and Twig), I only occasionally need to update the frontend. But then all these problems keep popping up.
Oh, that's the wrong yarn version. Oh, I thought v3 is the newest? But we still use v1? I used v3 in another project. So I need to install different versions? Ah, then I also need different versions of node? Ah, better to use nvm? Because only later versions have corepack, the experimental but recommended tool?
Or do we change back to npm? And why does an install process change a .lock file?
- Yep.
Don't want these marketing emails? Unsubscribe here.
Oh, you need to login in order to do that.
No, that's the wrong password for your account. Forgot password?
Hm, we don't see your account existing. Probably a different email address?
... sigh... sent a couple of emails to the data protection contact listed, but after 5 years, I still get the emails and I occasionally try to login again.
So I just automatically mark it as spam every time.
But probably because they're a small provider and don't have the resources; this is the largest telecommunications provider in Germany.
- > You're just trading doing stuff in the frontend for doing stuff in the frontend + backend. Might make sense in a lot of cases, while not making sense in other cases.
For me I can now do everything in the backend, I don't need to switch context (Twig templating language vs. JavaScript / SPA / etc). It's now easier to just keep up to date with PHP / Symfony, instead of also updating Node, npm / yarn, node_modules, and keeping up to date with everything.
Otherwise the frontend part is messy and not so great code, since my JS skills are limited and it's too stressful for me to keep up to date with in addition to PHP / Symfony (I had worked with AngularJS 1, Angular 2-8, Vue 2, some React, played around with Svelte, managing stuff via bower, gulp, grunt, Webpack, parcel, npm, yarn 1/2/3, Node 10-18, nvm, corepack; and if I kept up, I probably need to look at bun soon).