bmulholland's comments

Intel Mac Pros max out at 1.5TB of RAM, and these are max 192GB. Seems like a large drop. I've heard that Apple Silicon is more memory-efficient, maybe because of efficiencies from the tight integration with macOS. Is that enough to make up for the difference?

I used Chef's Plate in Vancouver ~5 years ago, and it was the best meal kit service I've tried. The recipes were varied, and often had unique ingredients or garnishes that I'd never have tried otherwise. None of the meal kits in Germany match that level of quality or uniqueness.

This is an interesting question, but a bit vague and therefore hard to answer. Some of the articles that come to mind are quite timeless, such as Schlep Blindness. Do you have some particular articles in mind that you think are outdated? Which? Why?

Recital | Remote (Global, core hours: North America mornings) | Full-time | https://recital.software

Recital is the negotiation workspace for contracts professionals. We’re building a web app that brings standard development tooling to the world of contract negotiations, with features analogous to version control, diffs, and other common IDE features.

We're a close-knit, global, cross-functional team, part of an early-stage, all-remote startup. It's our second startup in the space (the first was acquired). We follow modern product management (discovery) & development (DORA) practices, emphasize developer experience as an accelerator of customer value, and use provably effective management techniques (à la Manager Tools). You can read more about our team at https://recital.software/working-at-recital/

We're looking for an intermediate+ full-stack developer specializing in CSS, and for a backend developer (almost a data engineer) specializing in data management and background jobs.

Read more at https://recital.software/careers/

Recital | Remote (Global, core hours: North America mornings) | Full-time | https://recital.software

Recital is the negotiation workspace for contracts professionals. We're bringing the table stakes of today's programming world to contract negotiations, such as easy version control, diffs, and other features you'd find in an IDE.

We're a small, early-stage, global, all-remote startup. It's our second startup in the space (the first was acquired). We follow modern product management (discovery) & development (DORA) practices, emphasize developer experience as an accelerator of customer value, and use provably effective management techniques (à la Manager Tools).

We're looking for intermediate+ full-stack developers (specializing in CSS) and data engineer generalists.

https://recital.software/careers/

I had to switch from Render to Heroku a year or so ago because Render had no security documentation at all. I asked them about it at the time and was told security docs were perhaps six months out. There's still none, so it's clear that demonstrating security is not something that's a priority.

Recital Software | Lead Frontend Engineer, Lead Backend Engineer | Fully Remote | Full-time | https://recital.software/

Our mission is to accelerate the negotiation of commercial contracts and enable in-house counsel to do their most valuable work. Unlike other approaches, such as CLM (Contract Lifecycle Management) systems, our product lets negotiators continue to use the tools they're familiar with: Word and Outlook/Gmail. We have a previous exit with an adjacent product (Contractually -> Coupa). Our MVP aggregates the documents and emails that they would otherwise have to search for across multiple tools.

You'll be the owner of the entire <frontend/backend> application, continuously improve the application and yourself as we grow, put in place best practices, and <frontend: establish a coherent design/backend: establish infrastructure as code>.

Apply at https://angel.co/company/recitalsoftware/jobs

Recital Software | Lead Frontend Engineer, Lead Backend Engineer | Fully Remote | Full-time | https://recital.software/

Our mission is to accelerate the negotiation of commercial contracts and enable in-house counsel to do their most valuable work. Unlike other approaches, like CLM (Contract Lifecycle Management) systems, our product lets negotiators continue to use the tools they're familiar with: Word and Outlook/Gmail. We have a previous exit with an adjacent product (Contractually -> Coupa). Our MVP aggregates the documents and emails that they would otherwise have to search for across multiple tools.

You'll be the owner of the entire <frontend/backend> application, continuously improve the application and yourself as we grow, put in place best practices, and <frontend: establish a coherent design/backend: establish infrastructure as code>.

Apply at https://angel.co/company/recitalsoftware/jobs

> If you want to change people, then give them positive reinforcement. If you try to "change" others by negative feedback, they will likely do less of everything and try not to be caught doing anything because it might be the "wrong thing".

Which is why Manager Tools emphasizes that this form of feedback should be used first exclusive with /positive/ feedback for quite some time (months) before using the format for negative feedback. And that, once started, positive feedback should outweigh negative feedback 3-1.

Yes: practically, it just might not be a good time, and emotionally, it prepares the person to accept the feedback. Less so in the book, but definitely on the podcast, they really emphasize that the question is genuine; if someone says no to the question, then you accept the no and move on.

They also emphasize that you should give /only/ positive feedback for quite some time before starting to give negative feedback. That would probably go a long way to soften things enough that one feels they can say no when appropriate.

(There's a whole set of things to do if the direct /always/ says no, of course)

Germany ordered 10,000 ventilators from a domestic manufacturer, though with delivery "over the next year" so it's unclear what the schedule will be.

Everything else aside, it really feels like this article purposely stretches out the first example and compresses the second:

* Joe gets told to work on his own, and only briefly consults a co-worker once. Janelle sits down with a senior dev and works through it together. How much of Joe's work could have been solved by sitting down with a developer?

* Every single command Joe writes out is included in the article, while docker steps (potentially more than one) are summarised with a sentence, e.g. "she just needs Docker on her system."

* Every time Joe has a problem, he has to figure it out on his own, google it, etc. Janelle just gets things pointed out to her by Rebecca.

Seems like a pretty biased comparison, even if the point is valid.

Pivotal Tracker is great for what it's intended for, but it's a very opinionated tool. It's not a good repository for storing a large number of bugs or features, and as such doesn't have fancy features like "X blocks Y".

If you have an external system for your features (we just use a google docs roadmap) and immediately triage bugs (will fix next sprint, or won't fix), it works great. Lots of discipline required, though, and it takes some understanding of their specific approach before things start to make sense.

I have added my email to my profile

For what it's worth, we're hitting many of those same problems even without lite. People are finnicky about how their contracts look, and they tend to spend a lot of time getting them to look just right. It's especially difficult with the jump from Word to HTML, even when it's abstracted via e.g. CKEditor.

May I ask where you work?

lite is a plugin for CKEditor that is built on top of ICE: https://github.com/loopindex/ckeditor-track-changes/#track-c...

We are using CKEditor, but are not currently using lite. Our version compare is done separately using an HTML diff engine. We have a number of requests for redlining-as-you-type, which we don't currently do, and will probably implement that with lite when we get to that.

I have implemented it as a proof of concept twice now, but keep finding bugs and issues that block us from releasing it as a feature. Seems like you might be hitting some of those as well?

My recommendation would really come down to what issues your legal-focused clientele have with the current solution. If it's accuracy, storing each version in its entirety and comparing those versions is basically what lawyers do today with Word.

I'm the lead developer at Contractually (a Vancouver-based startup): http://www.contractual.ly. We take contracts out of Microsoft Word and email and put them in an online format that understands the business data and process that is involved. We're solving problems form the low level (version tracking, redlining, commenting) to the high level (renewal reminders, workflows, tagging, reporting). We're currently focussed on large businesses and enterprise.

To answer your question, there's not many startups in the legal space because people and businesses are really worried about their contracts. The conservative nature is one that needs to slowly be eroded, and that's where we're at now. E-signature providers have taken away a lot of concerns and we're starting to see opportunities in areas outside of just signing.

At Contractually, we're seeing more competition (a good thing, of course) targeting small businesses right up to enterprise. Typically, they solve some small part of the contracts problem: Assembling documents, or e-signatures, or workflows, etc. The competition isn't just coming from startups (e.g. glider.com, acquired last year), it's also coming from large incumbents (e.g. Merrill DataSite for contract management, launched last month).

It's an exciting time and I think we'll start to see big chunks of the problem solved over the next few years.

We are solving many of the same problems at Contractually [0]. Word import, contract generation, private editing, version control, redlining, commenting, e-signatures, and more.

[0] http://www.contractual.ly/