The biggest weakness in the study is that Taxi and ambulance drivers in the dataset died around 64 to 67, versus 74 for other occupations [0]. If Alzheimer's is much more likely to show up later, then lower Alzheimer's related death rates among Taxi and ambulance drivers may reflect earlier mortality rather than any effect from the job.
This isn't theoretical. In my 20 years in retail and logistics, I've seen these libraries repeatedly fail in production. Real world examples include:
* Invoices: Totals get pushed to a new page with no repeated <thead> header. This is a classic failure of CSS table rendering across page breaks. properties like page-break-inside: avoid are notoriously inconsistent in browser print to PDF engines. Line items get split mid row because the engine doesn't understand the semantic integrity of the data.
* Bills of Lading & Manifests: These documents are infamous for unpredictable page breaks. One page cuts a row in half, the next duplicates headers, the next drops content entirely. This often stems from complex flexbox or grid layouts that the PDF rendering engine struggles to paginate deterministically.
* Shipping Labels: A barcode or QR code shifting by a few pixels is often a DPI or scaling artifact. The browser rendering at a logical 96 DPI doesn't translate perfectly to a 300 or 600 DPI thermal printer format, introducing rounding errors that are catastrophic for scanners. Addresses drift outside the printable area because CSS margins (margin, padding) can be interpreted differently by the print media engine versus the screen engine.
* Digital Forms: This is a classic failure of absolute vs. relative positioning. When you overlay HTML form fields on a scanned PDF background (a common requirement), the HTML box model's flow layout simply cannot guarantee pixel-perfect alignment with the fixed grid of the underlying image. I've seen teams resort to printing, using white out, and hand filling forms because the software couldn't align (x, y) coordinates.
* Tickets & Passes: Scanner rejection due to incorrect sizing is often due to the browser engine's "print scaling" or "fit-to-page" logic, which can be difficult to disable and varies between environments (e.g., a local Docker container vs. an AWS Lambda function with different system fonts or libraries installed).
This always turns into a long tail of support tickets. The only truly reliable solution is to bypass the HTML/CSS rendering model entirely and build the document on a canvas with an absolute coordinate system. This means using libraries like FPDF (PHP), ReportLab (Python), or lower-level tools like iText/PDFBox (Java), where you aren't "converting" a document, you are drawing it. You place text at (x, y), draw a line from (x1, y1) to (x2, y2), and manage page breaks and object placement explicitly.
It's not cheap. The initial build cost is high because every layout is effectively a small, “programmaticd CAD project”. You can't just "throw HTML at it". But the payoff in reliability is immense. It becomes a set and forget system that produces identical documents every time, which stops the endless firefighting.
Yes, two years later it can be painful to update when the original developer is gone. But I would take that trade off any day over constantly battling with imprecise, non deterministic tools. In twenty years of building systems where documents are mission critical, "close enough" rendering was almost never good enough.
Diátaxis is a great way to structure documentation, but I think its real value is in simplifying how we think about writing docs.
It shifts the focus from trying to cram everything into one ‘perfect document’ to recognizing that different users have different needs.
Like, tutorials are for learning by doing, guides are for solving specific problems, reference is for quick lookups, and explanations dive into the ‘why.’
That clarity alone can make one write useful docs.
That being said, sticking too rigidly to any system can be a trap.
A great companion read is Martin Fowler’s “Accounting Patterns”[1]. Having built and maintained systems that manage financial events for over a decade, I wish I had read these patterns earlier.
Article | Software Engineer | Vancouver, BC | ONSITE, VISA | C$90 - C$160 | https://www.article.com
Article is on the mission to engineer remarkably better furniture experiences. To accomplish this goal we manage ourselves relationship with the factories and suppliers, ocean shipping, warehousing, customer service, quality assurance, operations, transportation network and final mile delivers.
We are building software systems to make an impact on each and every aspect of above mentioned areas. We are fast growing startup and we were recently named Canada's fast growing startup[0]. Come help us build remarkably better furniture experiences.
We are hiring for following positions:
Software Engineer,
Senior Software Engineer,
Principal Software Engineer
Article | Software Engineer, Product Manager | Vancouver, BC | ONSITE, VISA | C$80 - C$150 | https://www.article.com
Article is on the mission to engineer remarkably better furniture experiences. To accomplish this goal we manage ourselves relationship with the factories and suppliers, ocean shipping, warehousing, customer service, quality assurance, operations, transportation network and final mile delivers.
We are building software systems to make an impact on each and every aspect of above mentioned areas. We are 5 year old startup and we are growing at exponential rate. Come help us build remarkably better furniture experiences.
Article | Software Engineer, Product Manager | Vancouver, BC | ONSITE, VISA | C$90 - C$140 | https://www.article.com
Article is on the mission to engineer remarkably better furniture experiences. To accomplish this goal we are manage our own factories, ocean shipping, warehousing, customer service, quality assurance, operations, transportation network and final mile delivers.
We are building software systems to make an impact on each and every aspect of above mentioned areas. We are 5 year old startup and we are growing at exponential rate. Come help us build remarkably better furniture experiences.
We are hiring for following positions:
Software Engineer
Front End Engineer
Principal Software Engineer
Product Manager
If you really care about your customer you should be worried about false positive. I hope as a business you do not cancel customer orders because your fraud detection system has flagged them.
Depending on your scale you may using 3rd parties like Sift science, Stripe Radar or Roll your own fraud detection system.
Flagging orders as potential fraud is the easier part these days. The difficult part is how to come up with a process to verify these flagged orders. This process need to be simple and quick. Because essentially you are saying to your customer we think you are a fraud and can you prove that your not.
Banks merchant checks to verify flagged orders is extremely cumbersome. They require you to call a special phone number (which is different for each bank) provide customer Name, Billing Address, Billing Phone and Credit Information. Then they can only give you a response whether it is a match or not. They can't tell you whether it has been reported stolen or anything else for privacy reason. At scale this is a very time consuming process. It becomes even more cumbersome if you are security conscious business and do not store customer credit card information. In that case you have to communicate with the customer asking them to call you to provide your credit card information again.
There are solutions like 3D Secure but they are not widely supported and adds its own problems. It is high time credit card companies start providing merchant with a 2nd factor check for transaction. For example maybe once a transaction is placed with a merchant. They can trigger a 2nd factor check where by the bank automatically send a code to their email/phone number on file. If the customer is able to provide a correct code merchant can proceed with the order.
Fraud detection will always remain a point of contention between customer and businesses. I just hope business make sensible decision based on their situation. For example I have seen legitimate customer with all the above cases mentioned in the article.
Article | Software Engineer, Engineering Manager, Product Manager | Vancouver, BC | ONSITE, VISA | C$90 - C$150 | https://www.article.com
Article is on the mission to engineer remarkably better furniture experiences. To accomplish this goal we are manage our own partnership with factories, ocean shipping, warehousing, customer service, quality assurance, operations, transportation network and final mile delivers.
We are building software systems to make an impact on each and every aspect of above mentioned areas. We are a profitable 5 year old startup and we are growing at exponential rate. Come help us build remarkably better furniture experiences.
"Since Casper launched its “mattress in a box” concept in 2014, digital-savvy entrepreneurs have been launching new mattress brands online seemingly every week."
Casper was not the first mattress in a box online company. But Casper definitely is the first company to get the marketing right.
I do not have lot of experience in SaaS. I do have experience dealing with conversion rate in ecommerce. I believe you usually cannot compare conversion rate across different businesses in different markets. Comparing SaaS businesses in different markets is like comparing apple and oranges.
Actually that is not true in BC, Canada. According to BC Emergency Health Services [1], It charges a fee of $50 if transportation is not required. $80 if transportation is required.
How does this experiment methodology account for cross device mixed experience? Because of the multiple devices use, There will be lot of users that have seen both variation.
Hey, we’re Article. We’re a digital-first furniture brand that’s re-engineering the furniture experience one sofa at a time. We don’t have brick and mortar stores, so we’re able to deliver remarkable value on beautiful, modern furniture. Because of this, we’re growing like crazy and we need a few more hands on deck. Maybe it’s you we’re looking for?
We’re looking for a Principal Software Engineer to Lead and own the end to end ownership of architecting, designing, developing, and deploying Article supply chain platform.
You will significantly impact the Article business by:
- Designing and building Article supply chain software platform.
- Being the gatekeeper for the repository by performing code reviews.
- Taking ownership of the up time of all software services.
Understand business needs and specs out detail software solutions.
- Being the advocate for good quality code and best practices.
- Improving team velocity by being the force multiplier for the team.
Please feel free to reach out to me personally at tahseen at article.com.
In my experience Amazon SES is great if you only used it for transactional emails. If you start sending marketing emails you will soon find yourself being blocked by ISPs and email service providers. You will end up spending a considerable amount of time getting yourself unblocked. Some service providers will even block the domain name, so even switching the service won't help you. Everything will go to spam from that domain name.
I have built the tech for an ecommerce startup (https://www.article.com) from scratch. Using different services for transactional and marketing emails is probably one the best decision i made early on.
Pro Tip #1:
"Use a different domain name for the from address while sending out marketing emails"
For example if your primary domain is example.com. Use [email protected] as your from address in transactional emails. Use [email protected] as your from address in your marketing emails. Off course forward all emails received by [email protected] to [email protected] (Why? see Pro Tip #2).
Pro Tip #2:
"Never use fake emails like [email protected] for the from address for any email you sent. Yes not even for marketing emails"
You will be surprised how many time customer just reply to emails they have received even if it is an unrelated marketing email. You will regularly see customers receiving a monthly newsletter and they will hit reply asking "Can you change the shipping address on my order?"
I have being using Chrome Profile(People) feature since they were introduce. It has been a god send for me. I tried Firefox containers for a couple of days here a couple things that will really help:
* Containers need to be per window. Keeping track of containers at Tab level is lot of mental work.
* Set a different default container per device. For example I want to set different default for an office laptop, home computer, shared device, etc.
Firefox is getting there i feel it is just moving too slow for me to make a complete switch.
For example:
caffeinate -dimsu
That keeps the Mac awake so I can use Claude remotely from phone.
You can also wrap your command as well, but I rarely use it.
caffeinate -dimsu your-agent-command