Software Engineering

Software Engineering

1635 bookmarks
Newest
weinre - Home
weinre - Home
It's a debugger for web pages, like FireBug (for FireFox) and Web Inspector (for WebKit-based browsers), except it's designed to work remotely, and in particular, to allow you debug web pages on a mobile device such as a phone.
weinre - Home
InfoQ: Patterns for Continuous Delivery
InfoQ: Patterns for Continuous Delivery
Continuous Delivery can be applied to companies of any size, but the exact process is going to differ widely from company to company. Clearly the needs of a four-man team that handles everything is going to be different from that of a large, multi-team company with formal QA and a well-equipped production support department. Rather than try to make a one-size-fits-all solution, this white paper will cover a variety of scenarios and options.
InfoQ: Patterns for Continuous Delivery
Scott Chacon on the Interwebs
Scott Chacon on the Interwebs

So, what is GitHub Flow?

  Anything in the master branch is deployable   To work on something new, create a descriptively named branch off of master (ie: new-oauth2-scopes)   Commit to that branch locally and regularly push your work to the same named branch on the server   When you need feedback or help, or you think the branch is ready for merging, open a pull request   After someone else has reviewed and signed off on the feature, you can merge it into master   Once it is merged and pushed to ‘master’, you can and should deploy immediately

Scott Chacon on the Interwebs
Holland Backup Project | Backed the #$%& Up!
Holland Backup Project | Backed the #$%& Up!

Holland is an Open Source backup framework originally developed at Rackspace and written in Python. Its goal is to help facilitate backing up databases with greater configurability, consistency, and ease. Holland is capable of backing up other types of data, too. Because of its plugin structure, Holland can be used to backup anything you want by whatever means you want. Notable Features Pluggable FrameworkSupports Multiple Backup SetsDatabase and Table Filtering (Using GLOBs)Auto-Detection of Transactional DBsSafe use of –single-transaction with mysqldumpIn-Line and Pluggable CompressionBackups Suitable for Point-In-Time Recovery / ReplicationMySQL + LVM Snapshot and Logical BackupsPostgreSQL backups using pgdump

Holland Backup Project | Backed the #$%& Up!
jedi4ever/veewee - GitHub
jedi4ever/veewee - GitHub

VeeWee: the tool to easily build vagrant base boxes Vagrant is a great tool to test new things or changes in a virtual machine(Virtualbox) using either chef or puppet. The first step is to download an existing 'base box'. I believe this scares a lot of people as they don't know who or how this box was build. Therefore lots of people end up first building their own base box to use with vagrant.

Veewee tries to automate this and to share the knowledge and sources you need to create a basebox. Instead of creating custom ISO's from your favorite distribution, it leverages the 'keyboardputscancode' command of Virtualbox so send the actual 'boot prompt' keysequence to boot an existing iso.

jedi4ever/veewee - GitHub
Dette Technique : il n’y a pas de pénalité à la rembourser en avance « DantotsuPM.com
Dette Technique : il n’y a pas de pénalité à la rembourser en avance « DantotsuPM.com

Une fois que ce point de basculement est déterminé, une société peut décider où et quand elle doit aborder les problèmes de qualité structurelle qui ont créé la dette technique. La partie agréable de se débarrasser de dette technique est la même que pour la dette personnelle: cela évite le paiement de plein d’intérêts. Pourtant, il n’y a aucune pénalité à rembourser en avance… en fait, cela apporte une récompense significative grâce à un logiciel de meilleure qualité.

Dette Technique : il n’y a pas de pénalité à la rembourser en avance « DantotsuPM.com
Why SourceForge Lost | Users in Hell
Why SourceForge Lost | Users in Hell
GitHub is a developer’s paradise, and they want to keep it that way. By avoiding the community-building features that most people like to do anyway, they can ensure that people keep their development efforts on GitHub. It’s a winning strategy.
Why SourceForge Lost | Users in Hell
devstructure/blueprint - GitHub
devstructure/blueprint - GitHub

Blueprint reverse engineers servers

Easy configuration management. Detect relevant packages, files, and source installs. Generate reusable server configs. Convert blueprints to Puppet or Chef. No DSLs, no extra servers, no workflow changes. Blueprint looks inside popular package managers, finds changes you made to configuration files, and archives software you built from source. It runs on Debian- and RPM-based Linux distros with Python >= 2.6 and Git >= 1.7. Move blueprints around with Blueprint I/O.

devstructure/blueprint - GitHub
HTML EMAIL BOILERPLATE v 0.4 updated 5/12
HTML EMAIL BOILERPLATE v 0.4 updated 5/12
Welcome to the HTML Email Boilerplate. This website and its sample code creates a template of sorts, absent of design or layout, that will help you avoid some of the major rendering problems with the most common email clients out there — Gmail, Outlook, Yahoo Mail, etc. While not plug and play (you know, you'll have to do some work ;-), it will provide some helpful examples and snippets that will keep your email design rendering as true-to-form as possible.
HTML EMAIL BOILERPLATE v 0.4 updated 5/12
Threat Risk Modeling - OWASP
Threat Risk Modeling - OWASP

When you start a web application design, it is essential to apply threat risk modeling; otherwise you will squander resources, time, and money on useless controls that fail to focus on the real risks. The method used to assess risk is not nearly as important as actually performing a structured threat risk modeling. Microsoft notes that the single most important factor in their security improvement program was the corporate adoption of threat risk modeling. OWASP recommends Microsoft’s threat modeling process because it works well for addressing the unique challenges facing web application security and is simple to learn and adopt by designers, developers, code reviewers, and the quality assurance team. The following sections provide some overview information (or see Section 6.9, Further Reading, for additional resources).

Threat Risk Modeling - OWASP