Recently, I was working on a legacy PHP project that synchronises LDAP teams and users. I found several bugs relating to poor DN “parsing” using regexes and string replacement.
There has to be a better way of doing it, I thought. Alas, there’s not much choice in the PHP ecosystem when it comes to parsing DNs. While there are a few libraries and even PHP’s own `ldap_explode_dn()`, I think they don’t have clean APIs.
So I wrote LDAP DN. It breaks down DNs into RDNs and attributes, supports escaping, allows basic manipulation and has 100% test coverage.
I charge regular clients (the ones that I do some work for every month) by the hour.
I use a spreadsheet to track my time.
Less regular clients, I estimate the project and bill them a fixed amount.
Shameless plug: For estimating projects I use a web app I built (https://estipad.com). It lets me break projects down into tasks and subtasks and estimate those instead of the whole project. It also generates a PDF that can go straight to the client.
Hi guys. I’m the founder and sole developer of Estipad.
Estipad is a web app that lets you break down a project into small tasks for easier estimation. When you’ve finished, you can download a PDF estimate ready to send to a client.
Estipad started as a basic CodePen that I used to calculate project estimates for my freelancing clients. A few of my developer friends liked it, so I decided to build it into a web app.
I’d love to hear your feedback and will happily answer any questions you may have.
Isn’t that against Google’s T&Cs? I’m sure a website is not allowed to present different content to GoogleBot than it does to regular users. Not sure if there’s a rule that says it can’t present different content when a user clicks on a search result vs goes directly to the website or from another referrer.
Not a lot but it’s something. And I built the validator without even thinking about monetizing so it’s quite nice to get rewarded with some pocket money.
It’s not 100% passive, as I do spend a little time maintaining it and adding new features, but what income is 100% passive?
I think the core of the framework needs to be written from the ground up. The core is the basis of Django’s API. Trying to mimic it on another framework’s core would hinder the development at some point.
Well, you could ask the same about Zend, Laravel or Symphony — what’s different between them? Even though they support most of the same features, they’re implemented in unique ways. None of them are like Django, though. I think it’d be cool to have a Django-like framework for PHP.
https://i.imgur.com/Ef1UpCv.png