recentpopularlog in

documents

« earlier   
How to Electronically Sign PDF Documents Without Printing and Scanning Them
Windows: Use Adobe Reader
osx/macos: built into Preview, as far back as 10.11
Linux/Android: It's Complicated(tm): use "Adobe Fill & Sign"
ios: built in
chromebook: use HelloSign
pdf  reference  business  documents 
12 days ago by mechazoidal
jung-kurt/gofpdf: A PDF document generator with high level support for text, drawing and images
A PDF document generator with high level support for text, drawing and images - jung-kurt/gofpdf
golang  pdf  generator  generation  documents 
17 days ago by pinterb
Diff tool for file comparison on Windows, Mac, and Linux - Diffchecker Desktop
Diffchecker is an online diff tool to compare text to find the difference between two text files
comparison  text  documents 
22 days ago by seb1980
GitHub - alephdata/aleph: Search and browse documents and data; find the people and companies you look for.
Aleph is a tool for indexing large amounts of both documents (PDF, Word, HTML) and structured (CSV, XLS, SQL) data for easy browsing and search. It is built with investigative reporting as a primary use case. Aleph allows cross-referencing mentions of well-known entities (such as people and companies) against watchlists, e.g. from prior research or public datasets.

For further details on the software, how to use it, install it or manage data imports, please check the documentation at:

https://docs.alephdata.org
tools  documents  emails  ocr  pdfs 
23 days ago by paulbradshaw
Find public records and leaks - OCCRP Aleph
Allows you to upload emails (if registered) and do entity extraction
Also can set up alerts for when entities appear in new document leaks

See https://docs.alephdata.org/guide/loading-data
emails  tools  leaks  Database  occrp  documents  alerts 
23 days ago by paulbradshaw
Voyant Tools
Voyant Tools is a web-based text reading and analysis environment. It’s designed to make it easy for you to work with your own text or collection of texts in a variety of formats, including plain text, HTML, XML, PDF, RTF, and MS Word. You can also work with an existing collection of texts like Shakespeare (click the “Open” button on the main page to see other pre-defined collections of texts).
text  tools  documents 
23 days ago by paulbradshaw
Quip
Quip is a new way of collaborating that fuels a culture of action. Empower your employees to get things done faster with less email, and fewer meetings.
online  documents  cloud  notes  collaboration 
26 days ago by kger
Scaling Engineering Teams via Writing Things Down and Sharing - aka RFCs
What if I said there is a way to tackle both these issues pretty well, using a few simple steps? A word of warning, one of the steps will sound a little crazy. Here they are:

Do planning before building something new. This can be in-person whiteboarding or just talking it through with the team members, as long as you're all clear on how you will get things done.
Capture this plan in a short, written document. Once it is clear to the team how and what you do, it should be relatively quick to write down the "how". Don't go overboard.
Have a few, select people approve this plan before starting work. Similar to how it's a good quality gate to only merge a pull request after someone does a review on it, it makes a huge difference if before starting work on a project, a few, relevant people validate the planned work. These can be senior engineers, people on a team who will use the feature and so on.
Send this planning document out to all engineers in the company and let anyone and everyone comment on it. Yes, this the step that probably sounds crazy.
Have everyone follow the above steps for every project that is beyond some super trivial complexity and iterate on a lightweight, RFC-like process so it works well for your org or company.
As unlikely it might sound, the above process both works and scales really well, from a handful of engineers to teams of thousands. It addresses not only issues on visibility or reducing tech/architecture debt, but also spreading knowledge and having engineers be more engaged day to day. This is the one, simple process I recommend any small or medium tech team to do, especially if they are in a growth phase. It's also the process we've successfully used and iterated on at Uber, going from tens of engineers to a couple of thousand ones.
...
To give an example, this is roughly how the backend and frontend (mobile/web) templates evolved about a year ago, since when we switched to generated templates:

Backend
————-
List of approvers
Abstract (what is the project about?)
Architecture changes
Service SLAs
Service dependencies
Load & performance testing
Multi data-center concerns
Security considerations
Testing & rollout
Metrics & monitoring
Customer support considerations

Mobile/Web
—————-
List of approvers
Abstract (what is the project about?)
UI & UX
Architecture changes
Network interactions detailed
Library dependencies
Security concerns
Testing & rollout
Analytics
Customer support considerations
Accessiblity
Iterating and customizing to the needs of the engineering team is key. In our case, the templates started to include important things we cared about.
software  methodology  architecture  dev  documents  design 
4 weeks ago by dstelow

Copy this bookmark:





to read