Skip to content

Instantly share code, notes, and snippets.

View sunnysidesounds's full-sized avatar

Jason R Alexander sunnysidesounds

16 followers · 11 following
View GitHub Profile
@sunnysidesounds
sunnysidesounds / App-Store-Connect-API-Python.md
Created November 29, 2021 22:10 — forked from corrieriluca/App-Store-Connect-API-Python.md
Connection to the App Store Connect API using Python3
@sunnysidesounds
sunnysidesounds / bloat_my_db.md
Last active October 21, 2021 21:59
[bloat_my_db] #all
  • Worked on a lot of tools teams.

PyScaffold

  • PyScaffold is a project generator for bootstrapping high-quality Python packages
  • Installation pip install --upgrade pyscaffold[all]
  • Pyscaffold creates a perfect project structure that compiles the best practices for Python packaging and has tons of useful defaults
@sunnysidesounds
sunnysidesounds / simplistic-ffmpeg-streaming.py
Created October 14, 2021 04:42 — forked from anthonyeden/simplistic-ffmpeg-streaming.py
Sending FFmpeg output to HTTP, via Python's Flash
"""
Streaming FFmpeg to HTTP, via Python's Flask.
This is an incredibly simple example, which will yield issues due to inconsistant input and output rates.
If you're going to use this, VLC works okay as a client.
You really need to move FFmpeg into a separate thread, which should help stream audio more consistantly to the HTTP client.
Example by Anthony Eden (https://mediarealm.com.au)
"""
from flask import Flask
@sunnysidesounds
sunnysidesounds / watchdog_example.py
Last active August 5, 2021 21:31 — forked from njanakiev/watchdog_example.py
[Python Monitoring Filesystem Script] #all, #watchdog
import sys
from watchdog.observers import Observer
from watchdog.events import FileSystemEventHandler
class EventHandler(FileSystemEventHandler):
def on_any_event(self, event):
print("EVENT - SEND FILE UPDATE")
print(event.event_type)
print(event.src_path)
print()
@sunnysidesounds
sunnysidesounds / pr-checklist.md
Created July 9, 2021 19:58 — forked from sherakama/pr-checklist.md
[Pull Request Checklist] #all, #pullrequests, #reviews, #checklist

When reviewing a pull request please check for the following

  • Unit Test provided
  • Does this require a behat test?
  • Deprecated code removed
  • Is all markup and styles accessible?
  • Syntax & Formatting is correct (Code Climate should take care of this)
  • Is the approach to the problem appropriate?
  • Can anything be simplified?
  • Is the code too specific to _ and needs generalization:
@sunnysidesounds
sunnysidesounds / pull-request-template.md
Last active January 9, 2023 19:52 — forked from Lordnibbler/pull-request-template.md
[Pull Request Template] #all, #pullrequests, #sample, #templates

Project Name

Details

Please include a summary of the changes contained within this PR. Please also include relevant motivation and context.

Task: https://jira.com/remove-or-replace

How to test?

Please describe the tests or steps you have taken to verify your changes. Provide instructions that can be reproduced.

@sunnysidesounds
sunnysidesounds / defining_user_stories.md
Last active July 8, 2021 20:11
[Defining User Stories] #all, #JIRA, #stories

Creating a user story

  • The goal is to outline a particular value to the customer that a team can deliver in an iteration using a few short sentences, ideally using non-technical language. While traditional requirements (like use cases) try to be as detailed as possible, a user story is defined incrementally, in three stages:
    • The brief description of the need
    • The conversations that happen during backlog grooming and iteration planning to solidify the details
    • The tests that confirm the story's satisfactory completion

What makes a great user story

  • They don't go into detailed requirements.
  • User stories can be written using the following template:
  • As a [type of user], I want [goal] so that I [receive benefit].
@sunnysidesounds
sunnysidesounds / review-checklist.md
Created March 9, 2021 21:13 — forked from bigsergey/review-checklist.md
Front-end Code Review Checklist

Review checklist

General

  1. Does the code work?
  2. Description of the project status is included.
  3. Code is easily understand.
  4. Code is written following the coding standarts/guidelines (React in our case).
  5. Code is in sync with existing code patterns/technologies.
  6. DRY. Is the same code duplicated more than twice?
@sunnysidesounds
sunnysidesounds / rest_api_design.md
Last active October 6, 2020 21:00
[Rest API Design] #all, #api, #design, #webservies

Software Architecture Series: REST API Design

  • REST API: Is the De Facto Standard API

API Basics

  • What is an API (Application Programming Interface) : A means for software components to communicate with each other.

API Types: (4 Types)

@sunnysidesounds
sunnysidesounds / panasonic_initial_interview_questions.md
Last active September 30, 2020 19:01
[Panasonic Initial Interview Questions] #all, #interviews

Panasonic Initial Interview Questions

Q: What about this product with CIRRUS/V2X is appealing to you? Why are you interested in working here? A: I'm interested in working at this divison of Panasonic because I want to work on a real-time data exchange platform like CIRRUS/V2X. At Expedia I worked on a team that handled huge amounts of real-time user interaction data we used this data to advertise and remarket to users offsite through the Google advertising platform. Since working on that team, I found that I had a passion and was good at this kind of work. I'd now like to apply what I've learned at Expedia and various other companies to a real-time data exchange platform, like CIRRUS/V2X. What better way to do this then doing real-time traffic management at Panasonic.

Q: What's the biggest application you've ever worked on? A: Expedia.com in 32 countries, 100 billion dollars in average yearly revenue.