UserNumber42

I think that's clear. I've done both and I'm curious to see what people think. Would you rather have:

$model = new Model($conn);

or

$dbRepository->save($model)

Pros and cons of either solution? What do you do and why?

I'm hoping to get some high-level help for my app. The requirements are pretty basic. It's basic relational data, and if I didn't need to keep historical data, it would be a few tables with hundreds of rows for each table. Where it gets a little tricky is that each column, or 'attribute', needs to have all it's historical data kept.

Where it gets a lot tricky is that the data needs to be able to be retrieved in year/quarter buckets. So if I need to be able to easily get the last value for each quarter. The way I've designed it is a config file with all the attributes I want and a script to automatically generate a table for each attribute. This works, but if I want to view an entity then I

I am trying to use an RNN network with LSTM cells to generate text as a fun project to help learn machine learning. Currently, I have my training data set up in the following format. If the data is "These are a few of my favorite things." and my sequence length is 5, my two arrays are

These -> (space)

hese(space) -> a

ese(space)a -> r

se(space)ar -> e

etc...

Every tutorial I'm reading has a similar step after this and this is where I'm confused. For example tihs tutorial has it like this:

https://github.com/jctestud/char-rnn/blob/master/char-rnn_trump_text_generation-TRAINING.ipynb

    for batch_ix in range(count):
        X = np.zeros((BATCH_SIZE, SEQUENCE_LEN, V

No matter what I'm watching or listening to, I have to kick the volume up a bunch when I watch your casts. This isn't that big a deal, but it's annoying, especially when an ad comes on and blows out my ears. Also, when a caster gets hyped, the screaming is really loud and then the rest of the cast is too soft. I think you need to look into some sort of digital compressor/limiter.

That's it. Overall I love your casts, keep up the great work. AND TURN UP THE VOLUME!

I'm sure there is but I don't know the right word to search so I can't find anything. I would love to be able to really plan my project down to the function level before I start coding. I know I can do this with literal code but it would be nice to have some sort of GUI like when designing a database schema. Thanks.

A quick note, the code I put here is pretty much psuedo code that represents the actual code I'm using. If there are minor typos please ignore them. What matters is the big picture here and the specific error I mention at the bottom of the code. All the code for this can be seen here:

https://play.golang.org/p/1LtLCrqBFE

I'm trying to learn Go by writing an API that returns JSON. The two 'non-refactored' functions are pretty basic. Take a request and insert the data into the database using a prepared statement. What is immediately obvious is that these two functions are very similar and there is a lot of code duplication.

Looking at the 'refactored' version I give an example of how I want

I actually use weed for medical reasons and I would love to buy it legally and have my money go to the state. What are my options?

We're starting a large project that involves a lot of data and all historical data needs to be stored for each field. Looking at redis' sorted sets seems like a great way to do this with using a unix time stamp as the score. There will be around a million data points initially and it won't grow that fast but it will grow slowly and steadily. Has anyone used redis in this way? How has it scaled? Is anyone using it as the main persistence data store? I hear rumblings about people using it as the sole persistent data store but I've seen more cautioning against it. Realistically it would be used along side a SQL database. That's about it. Any feedback is most appreciated.

I want to practice merging but all the examples I can find online are trivial one line examples. Are there any repos that are made to practice this so you can download the repo, then merge a branch that was specifically created for conflicts, and then practice merging? The more complicated the better. Thanks.