jpallen

First impressions are good! Couple of small bits of feedback:

- I only had the option to create a worktree from main. I'd like to be able to pick any starting branch. Not a big deal, I just told claude to checkout the branch I wanted as my first instruction.

- For some reason in the Android app the usual automatic capitalisation of the first letter in a sentence doesn't work. Claude probably doesn't care, but I like to type in proper sentences!

- It would be nice if the worktree names got semantic names, e.g. by running my first prompt through Haiku. Maybe that's not the order things are set up in though

There's a lot of negative feedback in this thread, so let me say I'm really excited to try this! I have caring responsibilities at home that means I'm constantly switching between my laptop and phone. Claude code web has been a very useful tool for this, but it's not a great bit of software. Omnara looks much more configurable and thought out. I've looked for various solutions to this problem that just work, and nothing else mentioned in this thread fits the bill. Your demo looks like it nails it - I'm excited to try!

What happens if you combine a full Dungeons & Dragons rules engine with an LLM to act as the dungeon master? Until the recent wave of reasoning models, the answer was mostly 'nothing coherent', but Claude 3.7 with thinking is very good at this! It will probably get rate limited with minimal traffic, but I have a demo up at https://lairsandllamas.com

This is very cool! It's not as impressive, but here is a video of me writing Game of Life only by speaking out loud to VS Code: https://www.youtube.com/watch?v=6NSplhZ0DlY

I did that by building an open source VS Code extension to interact with GPT3.5/4 directly from your editor: https://marketplace.visualstudio.com/items?itemName=Biggles..... It cuts out copy/pasting between ChatGPT and your editor, or writing any boiler plate code since you can just ask it to insert the code you want, or change the code you have highlighted. You can also talk to it directly using the Whisper API!

A lot of people are commenting about how gpt4 is better than copilot, both in terms of getting it to do exactly what you want and in the quality of response. I've also found this and so I wrote a simple VS Code coding assistant that uses gpt4 and let's you be direct in asking what you want it to do: https://github.com/jpallen/biggles. Maybe it can be useful to some of you too.

It also supports voice, which is a fun way to code!

Cogo | Full-Stack & React Native Software Engineers | Full or Part-time | REMOTE | EU Timezone | £47,000 - £75,000 | https://www.cogo.co/

Cogo build tech solutions that help businesses and consumers measure and improve their carbon footprint and impact. We’re looking for engineers who can help us quickly build well engineered features into our consumer app, in collaboration with product designers and behaviour scientists. We have lots of data to wrangle, and some complex models on our back-end, which all need to feed through into a quality UI and UX of the app.

We have two open positions:

- Full-Stack Software Engineer: https://cogo.bamboohr.com/jobs/view.php?id=99&source=aWQ9NDk...

- React Native Software Engineer: https://cogo.bamboohr.com/jobs/view.php?id=100&source=aWQ9ND...

Tech-stack: React Native, Typescript, Postgres, GraphQL

Cogo | Full-Stack & React Native Software Engineers | Full or Part-time | REMOTE | EU Timezone | £47,000 - £75,000 | https://www.cogo.co/

Cogo build tech solutions that help businesses and consumers measure and improve their carbon footprint and impact. We’re looking for engineers who can help us quickly build well engineered features into our consumer app, in collaboration with product designers and behaviour scientists. We have lots of data to wrangle, and some complex models on our back-end, which all need to feed through into a quality UI and UX of the app.

We have two open positions:

- Full-Stack Software Engineer: https://cogo.bamboohr.com/jobs/view.php?id=99&source=aWQ9NDk...

- React Native Software Engineer: https://cogo.bamboohr.com/jobs/view.php?id=100&source=aWQ9ND...

Tech-stack: React Native, Typescript, Postgres, GraphQL

https://www.ideaflip.com - it's nice and simple compared to e.g. Miro, and nicely recreates the offline collaboration feeling of working around a whiteboard

'if X is true then I expect to see evidence of X' is generally a reasonable assumption/prior. So not seeing evidence of X is evidence that X is false. It's not proof, but absence of evidence generally is evidence of absence, unless you have a specific reason to believe it's not.

I was part of creating the initial version of https://www.swapmyvote.uk/ that ran in the 2015 and 2017 general elections. My experience of it was that it was a slow ramp up, but the final week leading up to the general election got very exciting and busy. There's a fun kind of energy in working on something like this, where people get more and more engaged right up to voting day... and then an anti-climatic finish afterwards, when interest vanishes overnight.

I drive a van, and that absolutely has a blind spot on the far side from the driver, no matter what I do with my head. The problem is that there are no rear passenger side windows to look through, and you can't see into the blind spot through the front passenger window. A blind spot mirror helps partially, but it's disconcerting driving with a known blind spot.

It's an arbitrary number, but it's nice because one mole of atoms with atomic mass number X will weigh approximately X grams. This is exactly true for carbon-12 (and is what defines a mole).

Thanks! You've given me something new to try out :)

Nice post, and very close to my experiences with Dockerfiles for node.

To the author: could you elaborate on the differences between carbon and alpine base images please? I can obviously go look this up, but this was the one part of the guide that was new to me. Your description wasn't enough to give me a complete understanding, so perhaps you could explain a bit more about carbon and alpine? Thanks.

Not as a direct product offering from us, but we want to make sure it's always easy to get your work in and out of Overleaf/ShareLaTeX, and work offline, via things like git, GitHub and Dropbox.

Thanks for the suggestion! We have played around with pandoc as an option in the ShareLaTeX compiler, but we weren't able to get it working smoothly enough for us to be happy with it. But it's definitely on our radar.

The current plan is to base the new editor on the the ShareLaTeX editor, but bring in the good parts of Overleaf to it.

Yep, there's no way that we'd remove all of this! It's taken us a long time to build up that documentation, and it will continue to be maintained and updated.

Hey, James from ShareLaTeX here. We’re very excited about what this means for ShareLaTeX and Overleaf! The blog post says most of what we wanted to say, but all four founders from ShareLaTeX and Overleaf are around this evening (we’re in the UK) to answer questions if you have any. Give us a little while to reply though, since we’re all trying to have dinner too! :)

Thanks for the kind words about ShareLaTeX! It's always great to hear that people have enjoyed it.

The open source nature of ShareLaTeX isn't just about being good internet citizens, it's also been core to the ShareLaTeX business. As far as we can tell, it's only helped us to grow, from community goodwill, publicity, and onboarding for our onsite enterprise offering. We're very much bringing two thriving businesses together here, to get to where we want to get to quicker, without duplicating effort. And the open-source aspect is a strength that we plan to keep.

- James, ShareLaTeX co-founder

Around 200,000 monthly active users.

Do the instructions at https://www.sharelatex.com/blog/2013/04/02/using-your-favour... work for you? We've supported unicode and XeLaTeX for a while now, so what you've described should work, but it's hard to say without specifics (LaTeX can be difficult with these sort of edge cases, but if something is broken, please send us a small example to support@sharelatex.com and we can take a look).

Regarding the annotation features of Google Docs, this is something we're beta testing at the moment: https://www.sharelatex.com/beta/participate. Come and give it a shot and let us know what you think!

I can't give exact numbers, but we have a conversion rate in the (very) low single digits. It's plenty to support our costs and development team though (we're purposefully optimised for a healthy cash-flow positive business, rather than for massive growth). Our churn rate is pretty terrible compared to what most people would look for in a SAAS app, but that makes sense when you consider the academic yearly cycle, and that a lot of people only use LaTeX for a short period in their life while they are a student.

If you haven't seen, we're about to make these collaboration features even more powerful! Come join the beta if you're interested: https://www.sharelatex.com/beta/participate

We haven't taken any VC funding

This is awesome, great job! How long before we can write ShareLaTeX in ShareLaTeX? ;)

I once got as far as writing and http server that used the flexibility of TeX macros to turn headers like 'content-length:' into TeX commands that recorded their value, and then processed the incoming request as if it were TeX code. It wasn't pretty...

ShareLaTeX (www.sharelatex.com) | DevOps | UK | REMOTE | www.sharelatex.com

We're looking for someone for a DevOps role at ShareLaTeX, which is an online LaTeX editor with over 1 million registered users. We help academics collaborate more effectively, and make LaTeX easier to work with.

The technologies we use are Ubuntu, Redis, MongoDB, Haproxy, Nginx, Node.js, Jenkins and Docker. The job will involve responsibilities like:

* Modifying our Node.js services to work with different architectures as they evolve.

* Improving our auto-scaling solutions for our LaTeX compiling backend

* Management & maintenance of our infrastructure, including designing redundant architecture, and upgrades & security patches of services.

* Improving our CI and deployment process

* Testing and improving our backup & backup verification process, and emergency procedures.

* Keeping our emergency monitoring services tested and up to date

* Improving and automating the Docker build process of our open source and onsite package

We automate everything via Chef, have a lot of small Node.js services, and use automated testing as much as possible, so you should be comfortable with these types of technologies and approaches.

Some reasons you'd enjoy working for us:

* Most of our codebase is open-source and we’re big fans of free software.

* We’re agile (with a lower case a). We test everything (unit and acceptance), we have a CI build process, a full staging environment to play with, and we automate as much as possible.

* Working hours can be flexible to your needs.

* Remote is a first class citizen, all founders and employees work remotely.

* We’re a bootstrapped & profitable company with no outside investors which means no crazy business pressures. Code quality and user happiness comes first.

We're looking from someone in a UK-compatible timezone. While we keep flexible hours, we've found that having reasonably overlapping core hours is important for communication.

Send us an email: founders@sharelatex.com

ShareLaTeX (www.sharelatex.com) | UK | REMOTE | DevOps

We're looking for someone for a DevOps role at ShareLaTeX, which is an online LaTeX editor with over 1 million registered users. We help academics collaborate more effectively, and make LaTeX easier to work with.

The technologies we use are Ubuntu, Redis, MongoDB, Haproxy, Nginx, Node.js, Jenkins and Docker. The job will involve responsibilities like:

* Modifying our Node.js services to work with different architectures as they evolve.

* Improving our auto-scaling solutions for our LaTeX compiling backend

* Management & maintenance of our infrastructure, including designing redundant architecture, and upgrades & security patches of services.

* Improving our CI and deployment process

* Testing and improving our backup & backup verification process, and emergency procedures.

* Keeping our emergency monitoring services tested and up to date

* Improving and automating the Docker build process of our open source and onsite package

We automate everything via Chef, have a lot of small Node.js services, and use automated testing as much as possible, including our for cloud and onsite builds, so you should be comfortable with these types of technologies and approaches.

Some reasons you'd enjoy working for us:

* Around 80% of our codebase is open-source and we’re big fans of free software.

* We’re agile (with a lower case a). We test everything (unit and acceptance), we have a CI build process, a full staging environment to play with, and we automate as much as possible.

* Working hours can be flexible to your needs.

* Remote is a first class citizen, all founders and employees work remotely.

* We’re a bootstrapped & profitable company with no outside investors which means no crazy business pressures. Code quality and user happiness comes first.

Send us an email: founders@sharelatex.com

I plan to charge a small monthly (possibly yearly) fee to cover hosting, yes.

If there's demand for the front-end being open sourced, then yes. I suspect that the people who'd be willing to host the front-end would have an easier time just editing the Jekyll template YAML directly though, which is already open source: https://github.com/academicbio/academic-minima