Here is a code snippet of a class that I be interested to refactor. I was in doubt on how to proceed with the process of instantiation. The original ask was here. After think about it and heard some opinions I end up refactoring and splitting the instantiation in several constructors, one public ...
I have written this script that downloads two tables from the db, preforms an intersection on them and adds 2 new columns to the resulting table, and uploads the resulting table to the db. It's a bit slow and I realize my code is messy (I'm new to python and GIS). I suspect more steps can be done...
package connectionmysql;
import java.sql.DriverManager;
import java.sql.*;
import com.mysql.jdbc.Connection;
public class Connect {
public static void main(String args[])throws Exception{
Class.forName("com.mysql.jdbc.Driver");
java.sql.Connection con=DriverManager.getConne...
Previous iteration.
I think this is about as good as it's gonna get, but just for kicks, let's do one more round of iterations.
As before, it's a very simple substitution from Brainfuck to Ruby, with fancy things like joining duplicate lines into one and indentation.
Some things that bug me:
...
I'm using the Django tutorial for 1.8 & Python 3.4 and right now the page has Questions that can add multiple Choices, but Choices cannot access its corresponding Question:
#models.py
class Question(models.Model):
question_text = models.CharField(max_length=200)
pub_date = models.DateTim...
The proper way to use string interpolation in Ruby is as follows:
name = "Ned Stark"
puts "Hello there, #{name}" #=> "Hello there, Ned Stark"
That is the way I intend to always use it.
However, I've noticed something odd in Ruby's string interpolation. I've noticed that string interpolation ...
I think it's important to remember that T is not always the best name for generic types. This is definitely important to remember when you start numbering them...
public static Dictionary<T1, T2> UnionDictionaries<T1, T2>(Dictionary<T1, T2> D1, Dictionary<T1, T2> D2)
To make matters worse, y...
I'll start off by addressing the elephant in the room. It's been the better part of a year since the announcement that Code Review was graduating. In all those months, there haven't been any visible indications of change from us on the team. There are a few reasons for that, but they all come dow...
