usametov

Github.com ui .currently does not natively supoport search for multiple topic tags as of now. However their api allows you to query multiple tags. Below is a simple example to query github.com with ecs and go topic tags.

curl -H "Accept: application/vnd.github.mercy-preview+json" \
https://api.github.com/search/repositories?q=topic:ecs+topic:go

Response from the github can be rather verbose so lets filter only relavant info such repo url and description.

curl -H "Accept: application/vnd.github.mercy-preview+json" \
https://api.github.com/search/repositories\?q\=topic:ecs+topic:go | jq '.items[] | {url:.url, description:.description}'

paseaf

Definition (Code Smells) Code smells are common code anti-patterns which could and should be refactored.

This doc is summarized from Martin Flower's book Refactoring (the 2nd Edition).

Refactoring is all about Change

• You may inverse previous refactorings as software grows
• You may change names of a function/parameter/varible/... as you learn

How to use this doc

Go to a section of code smell, and the refactoring techniques to that smell are written in Pascal Case under the Solution section. Refer to the book's catalog to get detailed examples and explainations for each refactoring technique.

Table of Code Smells

bert2

Giving Sisyphus a Hand: How to Improve OOP with Functional Principles

Yet another rant about object-oriented programming, but mainly a collection of ideas stolen from functional programming to improve it.

ShaiYer

RESTful API best practices guide - by Shai Yerushalmi

Web API’s is a web development architecture which decoupling the client GUI from the database and the server’s logic. This architecture enables to serve the same interface to multiple clients running on various platforms. Also, the same application can communicate with multiple interfaces.

REST stands for Representational state transfer and its a stateless protocol over HTTP that provides the interactions with the resources stored in the database which contains four basic CRUD actions - Create, Read, Update and Delete.

Each CRUD interaction can be defined by combinations of the following:

scottwd9

Building Evolutionary Architectures

Chapter 1 - Software Architecture

Architecture is 'the important stuff, whatever that is' or 'the parts that are hard to change later'. An architect analyzes business, domain, and other requirements to develop solutions that satisfy a list of prioritized architectural characteristics (-ilities). We should consider time and change with respect to architecture, or evolvability.

Software ecosystems are in a state of dynamic equilibrium. New languages, tools, methods constant force new equilibriums to emerge (free OS, linux, + free operations, puppet, led to the shift to containers). The pace of change in technology is constantly and rapidly changing in unexpected ways. We should architect systems knowing the landscape will change. Make ease of change a principal of architecture, remove the 'hard to change' definition of architecture.

An evolutionary architecture supports guided, incremental change across multiple dimensions. Evolvability is a meta characteristic that

patrick013

Installation of Metamap Java API on Windows

---

Metamap is a tool to recognize the UMLS concepts in a text. For using Metamap, a UMLS license is needed. Sign up for a license at https://www.nlm.nih.gov/research/umls/ .

Using Metamap Java API you need:

• Metamap full version
  • For windows version, please download Metamap 2013 or Metamap 2014
  • Download link: https://metamap.nlm.nih.gov/MainDownload.shtml

davecan

After checking multiple tutorials I had to take pieces from each of the following to get this to work on my Win10 system:

• https://www.howtogeek.com/165268/how-to-add-open-powershell-here-to-the-context-menu-in-windows/
• https://www.tenforums.com/tutorials/60175-open-powershell-window-here-context-menu-add-windows-10-a.html

Basically it uses the steps from the first article, but under the background path from the second article. Neither article on its own worked for me.

Steps:

pascaliske

Useful git diff tools

Overview

• Word: docx2txt (brew install docx2txt)
• Excel: xlsx2txt
• PDF: pdf2txt (brew install poppler)
• Images: exiftool (brew install exiftool)

Setup

calaway

Git Branch Merging Best Practices

1. After you've selected a feature to work on, create a branch in your local repo to build it in.
   • $ git checkout -b calaway/short_description_of_feature
2. Implement the requested feature, make sure all tests are passing, and commit all changes in the new branch.
3. Checkout the master branch locally.
   • $ git checkout master
4. Pull down the master branch from GitHub to get the most up to date changes from others. If you practice git workflow as described here you should never have a merge conflict at this step.
   • $ git pull origin master
5. Make sure all tests are passing on master and then checkout your new branch.

• $ git checkout calaway/short_description_of_feature

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules