hochchristoph
Joined 11 years ago
Karma
39
Submissions
35
Member since
Nov 9
[ my public key: https://keybase.io/chh; my proof: https://keybase.io/chh/sigs/2iWXOfM_guU8bhvlEvDBtuOHxeNAG293OuvLuUB4338 ]
View on Hacker NewsRecent submissions
Comment · 7 years ago
SEEKING WORK
Experienced Frontend Designer & Developer.
- You are a backend developer and your stuff looks "functional", but not very pretty
- You don't want to deal with any frontend tech in your perfectly engineered backend system
- You want to build your product on an extensible design system for the long term
…I'm here to help.
Location: Austria
Remote: Yes
Technologies: Vue.js, Tailwind CSS, Storybook, Webpack, TypeScript, Sketch.app
Website: https://hochstrasser.io
Email: [email protected]
GitHub: https://github.com/CHH
VAT-ID: ATU68701078
Comment · 8 years ago
To me it's amazing how many of these things have been fixed in the last couple releases of PHP. They worked really hard to fix the flaws, and still there's more coming, like property types.
One thing I'm particular exited about is the "Preloading" RFC (https://wiki.php.net/rfc/preload), which fixes one of PHP's oldest weaknesses: That code that is used on every request has to be loaded everytime a request comes in. Sure, thanks to Opcache a file only has to be compiled once, but the loading of the compiled classes into memory still makes for some overhead. With Preloading, if you use a framework like Laravel or Symfony, all core framework classes could be loaded once on PHP startup.
Comment · 9 years ago
7 Reasons why WordPress for Your Startup Is Not Your Best and Smartest Option:
1) Self hosting stuff is always a major time sink, especially for small companies. Backups of files and DB, server OS updates, and security are all your problems. Shared hosting has incredibly old versions of software, like PHP5 or still MySQL 5.6.
2) WordPress will never be really secure, the way it's built prevents that. You will always worry if your site is susceptible to hacking and have to keep up to date with the latest security disclosures and update your site.
3) Prebuilt themes are a trainwreck when it comes to customization. Hyperspecific CSS selectors, inline CSS in style tags and attributes, shoddy PHP in templates without any real separation of template and business logic. That matters, because you don't want your site to look quite the same as everyone elses.
4) It's 13 years old and there are newer, more modern, and secure alternatives, like Ghost, static site generators, Squarespace, or Webflow.
5) CDN integration is nowadays a must, especially if you are global. Integrating a CDN into WordPress' media upload is a PITA.
6) Translating content is a major PITA in WordPress. There are newer systems that address that. Every major translation plugin in WordPress has some minor incompatibility with another plugin, e.g. Polylang didn't work well with WP Sync DB.
7) Custom field support out of the box is laughable. WordPress isn't any fun without Advanced Custom Fields.
Comment · 9 years ago
Wow. That's the typical Medium post in a nutshell.
Comment · 9 years ago
SEEKING WORK - Europe, On-Site
Your most productive developers are leaving suddenly and without telling you anything about their reasons? Churn eats away any team productivity?
A developer needs about 6-12 months after they are hired to be at their best efficiency. That means that even when a developer leaves and you immediately rehire, you do get at least a 50% productivity loss for more than 6 months — while paying them the same wage.
It doesn't have to be this way. Keeping your developers happy and reducing churn in your team makes you more revenue, increases the quality of your product's code, and improves your product's user experience. But it needs more than free food and pingpong tables.
I'm here to assist you. With 10 years of experience working as a senior developer, team lead, and product lead, I know what makes a developer happy and what doesn't.
---
Christoph Hochstrasser E: [email protected] T: +436649228651