Skip to content

Instantly share code, notes, and snippets.

View ericthomasca's full-sized avatar

Eric Thomas ericthomasca

View GitHub Profile
@ericthomasca
ericthomasca / collision.p8
Created January 23, 2025 23:34
PICO-8 Collision Function
--collision function
function collide(player)
local x1=player.x/8
local y1=player.y/8
local x2=(player.x+7)/8
local y2=(player.y+7)/8
local a=fget(mget(x1,y1),0)
local b=fget(mget(x1,y2),0)
@ericthomasca
ericthomasca / db_naming_conventions.md
Last active December 16, 2024 19:03
Practical Methods: Naming Conventions

Practical Methods: Naming Conventions

Source: SQL Server Central - Michael Lato

Summary

Everyone should establish some sort of naming convention for their SQL Server platform. It helps to ensure that developers and DBAs can easily find objects and communicate with one another. New author Michael Lato brings us the start of a series on organizing your SQL Server code with an article on naming conventions.


Naming conventions are used to streamline development when multiple developers are working on a single system, as well as to simplify ongoing maintenance during the Development Lifecycle. There are many different naming conventions for SQL Server, and no single convention is necessarily right or wrong. However, a single consistent naming convention should be followed within each database to reduce confusion and enhance usability. Ideally, follow a single naming convention throughout all SQL Servers in an organization.

{
"$schema": "https://raw.githubusercontent.com/jsonresume/resume-schema/v1.0.0/schema.json",
"basics": {
"name": "Eric Thomas",
"label": "Software Development Student",
"image": "",
"email": "[email protected]",
"phone": "",
"url": "",
"summary": "Future software developer with a background of finance and electrical systems.",