joshuanapoli

Time is not on his side.

Programmers have always made a living by automating ourselves out of business. Somehow, we're still doing pretty well.

Probably the person who came up with the idea remains the most invested in it, and they should to watch for number 5 “the right moment” to bring it up again.

I think that it’s easier to change jobs in the USA; we usually don’t have a contract for a notice period for leaving. But like anything important, changing jobs takes preparation and a lot of effort. One might say that they lack opportunity or have too many obligations, or one might say that they just haven’t finished preparing for the change.

Ok, that makes sense, and it gives an explanation for Elon’s large investment.

The higher bidder lost, in this case. The party’s message is also crucial.

Cumulus | Senior Full Stack Software Engineer | Waltham, MA or Houston, TX | ONSITE | Full-time | https://www.linkedin.com/jobs/view/3987534709

Cumulus Digital Systems is building the Internet of Tools platform to transform the industrial workforce to be fully connected and data-driven, significantly improving safety and productivity in maintenance and construction. Our goal is to eliminate accidents caused by poor work quality.

We are looking for a senior full stack software engineer to help improve the functionality of Cumulus's web and mobile apps. Your work will provide user experiences that adapt to diverse environments, such as data centers, offshore platforms, and more. We are looking for a senior software engineer, who has mastered their craft and keeps up-to-date with developments in their field.

We work from home, but need to be located near our office in Waltham, MA or Houston, TX, where we test our integration with industrial tools.

Tech: React, React Native, AWS

Reach out to us at careers+hn@cumulusds.com

I wonder if loneliness improves (at least correlates) creativity. Can I make myself inventive by becoming lonely?

A separate bucket per (enterprise) customer is useful for SaaS; it can help prove tenant isolation, and it can help with sharing data with the customer.

Cumulus | Senior Full Stack Software Engineer | Waltham, MA or Houston, TX | ONSITE | Full-time | https://www.linkedin.com/jobs/view/3987534709

Cumulus Digital Systems is building the Internet of Tools platform to transform the industrial workforce to be fully connected and data-driven, significantly improving safety and productivity in maintenance and construction. Our goal is to eliminate accidents caused by poor work quality.

We are looking for a senior full stack software engineer to help improve the functionality of Cumulus's web and mobile apps. Your work will provide user experiences that adapt to diverse environments, such as data centers, offshore platforms, and more. We are looking for a senior software engineer, who has mastered their craft and keeps up-to-date with developments in their field.

We work from home, but need to be located near our office in Waltham, MA or Houston, TX, where we test our integration with industrial tools.

Tech: React, React Native, AWS

Reach out to us at careers+hn@cumulusds.com

I think that the hope/dream here is to make end-to-end tests less flakey. It would be great to have navigation and assertions commands that are robust against simple changes in the app that aren't relevant to the test case.

Right now, it takes skill and labor to move descriptions between representations for business goals, engineering (where we have frameworks and linters, etc.), and external/customer facing documentation.

The customer is faced with an output from the design process. I think that we can turn that around now. Let customers edit part of the documentation, and let the AI adapt the system to their need.

I think we will go the other way: A person will write the documentation and the AI will build the system that delivers the described product.

I don't think that candidates should have to do a lot of pointless data-entry to apply. If the candidate has tooling to increase their reach, for a given level of time invested, all the better. I'd rather that they have a minimum of personal investment to get into the top of the hiring funnel. If we start an interview process, then that will require increasing time and energy investment from both sides as it gets closer to hiring (and continuing to ramp up, to a point, post hiring).

From the hiring side: I would like good candidates to use tooling to apply to jobs. Then I’m more likely to get an application from you. But the applicant better apply some quality control to their tooling. It’s a turn-off to get a LinkedIn “I’m excited about your job opening” message where the content isn’t correctly substituted.

However, I think that what is actually happening is that tooling is more often used by more desperate candidates.

Cumulus | Senior Full Stack Software Engineer | Waltham, MA or Houston, TX | ONSITE | Full-time | https://www.linkedin.com/jobs/view/3987534709

Cumulus Digital Systems is building the Internet of Tools platform to transform the industrial workforce to be fully connected and data-driven, significantly improving safety and productivity in maintenance and construction. Our goal is to eliminate accidents caused by poor work quality.

We are looking for a senior full stack software engineer to help improve the functionality of Cumulus's web and mobile apps. Your work will provide user experiences that adapt to diverse environments, such as data centers, offshore platforms, and more. We are looking for a senior software engineer, who has mastered their craft and keeps up-to-date with developments in their field.

We work from home, but need to be located near our office in Waltham, MA or Houston, TX, where we test our integration with industrial tools.

Tech: React, React Native, AWS

Reach out to us at careers+hn@cumulusds.com

The goal is fine-grained alignment with your customers or stakeholders. In the long-run this should make product development more effective, though it's probably not going to be the fastest way to accomplish any individual task.

I agree that using a hosted secrets manager is better than storing a random assortment of secrets in an .env file that's written right next to your source code. Just make a with-secrets shell script that checks your 2FA and fetches them into the environment as it starts your application.

This way, the opportunity to expose the secrets is more limited to the actual run-time of the application. You don't need to risk exposing your secrets every time you git push.

I'll give a +1 to Godot; my son and I had fun going through the 2-D game tutorial and customizing the game. We added some physics, and it was quickly hilarious.

Simpler game systems weren't flexible enough to capture his imagination. We also tried to get started with Unity, but we couldn't get past the first steps.

In a multi-tenant system, you might have one customer who drops a big job that creates a huge number of tasks. We'd like to process this as fast as possible, but not block the tasks of small jobs from other customers, which should normally be completed very quickly.

There are definitely critical times where the engineering team can make a big swing in the success of their larger organization. I think that these intense periods naturally invite excitement. Going back to "normal" at the end of such a period is actually pretty hard; the work may not seem as important to the team, yet we have to rebuild some types of quality that were lost during the intense period.

Cumulus | Senior Full Stack Software Engineer | Waltham, MA or Houston, TX | ONSITE | Full-time | $115k—$165k | https://www.linkedin.com/jobs/view/3987534709

Cumulus Digital Systems is building the Internet of Tools platform to transform the industrial workforce to be fully connected and data-driven, significantly improving safety and productivity in maintenance and construction. Our goal is to eliminate accidents caused by poor work quality.

We are looking for a senior full stack software engineer to help improve the functionality of Cumulus's web and mobile apps. Your work will provide user experiences that adapt to diverse environments, such as data centers, offshore platforms, and more. We are looking for a senior software engineer, who has mastered their craft and keeps up-to-date with developments in their field.

We work from home. However, we need to be located near our office in Waltham, MA or Houston, TX. We test integration with industrial tools in the office.

Tech: React, React Native, AWS

Reach out to us at careers+hn@cumulusds.com

The situation varies from state to state. In Florida, many businesses are required to have public restrooms. So you should be able to do your business without being coerced into buying that $10 drink.

The JavaScript ecosystem historically had a lot of turnover. Probably there are a lot of applications that repeatedly ported over the years: Ruby to JavaScript, to coffescript, to flow types (for React), to Typescript.

I think that these language ports aren’t as disruptive as architecture changes (waffling on microservices), and they’re driven by availability of talent. Porting to follow the trend makes it easier and much more pleasant to onboard new developers. It usually has a practical benefit to users, because the latest tooling usually has a performance edge, but doesn’t support the old language.

I think that underground or earth bermed homes are often failures. There are different water and ventilation concerns for these. An above ground home is pretty accessible for repairs, but these can be nearly impossible if the home is underground.

Maybe they are thinking about embedding a program generator and execution environment into their LLM inferencing loop in a tighter way. The model invents a program that guides the output in a specific/algorithmic way, tailored to the prompt.

I haven't used Magit or GitUp, but I really appreciate JetBrains IDE automatic conflict resolver.

I like rebasing too. When I have any significant change, I usually end up making a mix of clean-up and preparation around my new feature. I like to move the separable parts into separate branches, so that there is less to review per request.

We started selling services in earnest alongside our SaaS product this year, and it’s working out well. We didn’t think of doing this during ZIRP; it was relatively easier to invest in more rapid product development.

It is much easier now to scale services (microservices, FaaS, etc.) to meet high or fluctuating demand than it used to be. So there are fewer cases where there is much to gain by carefully controlling how messages are buffered up.