At a high level, these are the steps.
For details of each step, see Option 2.
This is another one of those things that every developer has an opinion of. Can't blame them us really. As much as programming is science, it is also an art. And artists have their own temperaments.
Regardless, unlike artists, developers have to work as a team. That means that they have to follow the team's conventions regardless of their preferences.
Many conventions can now be easily enforced via configurations settings, thanks to the ubiquity of VS Code and, to a lesser extent, Prettier.
This article looks at the easy steps we can take to enforce coding conventions easily for a Next.js project.
In a previous article I wrote about my Git branching strategy for small teams. In this one, I will look at the topic of writing commit messages. This is also a highly opinionated take, just like the previous article.
I'm preparing a set of materials for a batch of interns whom I will be mentoring for a software development project.
One of the things that they will be doing is to check out an existing codebase to work on. To do that, they need to know Git.
I'm quite certain that the basics of checking in and out code is no problem for them if they have any Github profiles. However, every organization has its own conventions and requirements when it comes to maintenance of their codebases. This post documents my preferences in code maintenance.
This post is a knowledgebase article on Prisma with PostgreSQL.
The typical model in a Prisma schema has an id field that auto-increments:
model User {
id Int @id @default(autoincrement())
name String
}
The following is working (most of the time) code that inserts a new entry:
prisma.user.create({
data: { name: 'Some User' },
});
However, the following error may occur:
Unique constraint failed on the fields: (id)
This is baffling - if the field auto-increments, how can the unique constraint be violated?
With a little bit of programming, your site made by Docusaurus can be modified to be accessible only to users signed in to Google.
The source material came from this article by Thomasdevshare. His article describes a similar authentication scheme for Docusaurus with Firebase as the identity provider whereas this article describes the same approach using Google API directly.
I've been writing JavaScript for the past 10 years for my work, and there are still things in the language that trips me up. A very good example is on binding.
Given the setup below, I would have been a little hesitant as to what the right answer is.
I've recently had the opportunity to work with some remote teams to collaborate on a project. One question that cropped up was how do I pass the project specific changes to the remote team members without committing the credentials to the repository.
Some time back when researching for Backbone JS stuff (I can't remember for what now), I encountered this post Lessons learned while working with Backbone.js.
This post was written a few years back, but I was still able to glean some gems from it. Specifically, the section "Simplified Object Copying" was something that could be applied on plain vanilla JavaScript.
Backbone events are a powerful way to write responsive user interfaces with fewer lines of codes. This article attempts to give a detailed breakdown of the events and the parameters available for the callback functions.
The results in this article are applicable for version 1.2.3 of Backbone.js
The test is performed by instantiating instances of
ExperimentModel extended from
Backbone.Model and ExperimentCollection
extended from Backbone.Collection.
The model is first added to the collection to test "add" on the collection and then a properrty is set on the model.
var expModelA = new ExperimentModel({ id: 'a' });
var expCollA = new ExperimentCollection();