While I think successful folks do a fair share of "rewriting history" especially about spots in their timeline which could be considered "mean", I would much prefer PG's optimistic view. It keeps me more hopeful and that I could make the harder choice to be a good person for long-term success than to be a bad one for instant gratified returns. There's no problem in being hopeful and I welcome such positive "opinions".
I have to say that I've been a big Django user and have been using 1.7.x for a bit in my own development. There are a couple of "oddities" for me that perhaps folks will encounter:
1. If you do heavy TDD, you might not like that fact that you can't skip migrations the same way you previously could with SOUTH_TESTS_MIGRATE = False. There's a thread going on (https://groups.google.com/forum/#!topic/django-developers/PW...). It appears that with syncdb going away, there isn't an option available. I really hope there's a way to retain syncdb for unittest because I don't need to test database migration every time I run my quick unittests.
2. I think 'makemigrations' is a bit inconsistent at the moment. Sometimes it creates more than 1 initial files, sometimes it creates just 1 (if you run 'makemigrations app-name' instead of 'makemigrations')
There are a couple of other general Django issues, but those are the things I encountered while working with 1.7.x.
1. I think I'd like to see something like `./manage.py migrate --fresh`, which would forget about existing migrations, create a set in memory, and apply them. Pretty much emulating syncdb on a fresh database. Then the test runner could use that behaviour optionally (otherwise, RunPython statements may be missed that are required).
2. It may create more than 1 migration file if there are specific ordered dependencies afaik.
After squashing and migrating all existing databases, you can delete the old migrations files. The squashed migration becomes the new fresh migration that should usually contain just "CREATE TABLE" statements to be run on an empty database.
Using its best guess with dependency, it creates the appropriate migration file(s) favoring more files over potential conflicts. I think that's fine. The problem is consistency. However you choose to run the makemigrations, it should at least result in the same amount of files. It can't be more or less conflict if nothing is changed.
Not sure if it solves your problem, but in the dev version of Django you can use the `--keepdb` flag to `manage.py test`. This will preserve your test database after the test run, and only run any new migrations. It gives a real speed boost.
I wrote this on the home-bound train one night during a tough time with the startup. I assured you, no creative license here. The hours were pretty brutal on a couple of occasions. I made sure that everything is well supported at home first though.
I wrote this because I honestly was missing my daughter a lot and hope that capture that feeling and put it into words. I do my best to take care of my family and express my care to my love ones.
I think at the end of the day, we're all engineers, hackers, lovers etc. and it's our nature to solve anything that seems like a problem coming our way. This is why I decided to share it with everyone. Because I know that home-bound train, I wasn't by myself and there were others who were on it with me.
Thank you for your kind words to me. I am flattered and somewhat embarrassed when you call it "arts" though. I'm shy! I don't even call it poem because I didn't want to offend those who truly dedicate themselves to the craft. I'm simply a convert who wanted to share a feeling I captured.
If you can drop the stress at the office after 5PM, I think you should be feel blessed and I'm very happy for you.
I generally try to not miss dinner, but I have a rule that I go by, which is I never ask my colleagues to do what I was not willing to do myself.
Even if I spend all the time with my daughter, I never think it's enough. This was written when I made a decision to do both: be the best father I could and be the best professional at my job; when I did that, the only solution was to cut down on my sleeping time.
It was taxing on my body and one night on the way back on the train, I wrote this piece thinking about my daughter. I shared it because I didn't think I was the only one riding that home-bound train. I've been receiving personal messages telling me how much they appreciated me putting their feelings into words. That's when I knew I was definitely not riding that train by myself.
By the way, I left work early yesterday to take my daughter to the park yesterday. She was quite happy :)
I wrote this during a very tough run at the startup. Perhaps let me share a little bit more so that is it in context.
First and foremost, most credits, indeed go to my wife and family. The reason why I didn't mention my wife in this piece other than "You’re the only cool shade in the hottest of days/For a weary soul/that your Mother saved many years ago" is because this was a letter to my daughter. This piece was part of a collection of my thoughts from last year (when I was thirty) and I did thank my wife and family when I publish it: http://vuongnguyen.com/thirty-ba-muoi.html.
I'm 31 last month and I've been with my wife for 11 years now. We're best friends in many way and we support each other in our own dreams. Before my daughter was born, I was mostly doing consulting. I made sure I spent time walking and taking care of my wife. I made it a point to never miss a doctor appointment or any pregnancy/childbirth classes we have together. I really appreciated every step of the way.
Then my daughter was born, I stopped accepting new clients (as mentioned in the piece). Spent time with my wife and newborn. Then I stayed home for another three months with my daughter so my wife could return to work.
When I joined the startup, after much discussion and encouragement from my wife, I also made a promise to never miss any doctor appointment. That is still true. I feel blessed that I was able to afford much flexibility with my family and I never take it for granted. I know many other folks who go through a much more difficult time.
I think there is much more I could do and of course I'll continue to do my very best to be a good person every day. This was written as a personal thought and shared because I wanted to feel for myself and others, that we are not sitting alone on that home-bound train, if that makes any sense.
My wife and I have a pact: we'll live for our children and family but we'll always continue to develop ourselves. This way, there is never a resentment toward the people you love. I, too, work and go home for my family.
I've read everyone's comment thus far. Thank you for sharing your thoughts and for allowing me the honor to be part of your discussion.
I figured that we're not trying to find a correct answer here. But knowing our community of engineers, hackers, lovers etc. we'd always trying to solve any problems coming our way :)
My humble opinion is: feelings are honesty trying to express themselves. Even if we can't solve the problem of "feelings", I'm quite happy we can search for it together as a group.
I wrote this piece during a tough part of the startup last year. I recently looked at it again and realized it wasn't just about me but rather about all my friends, I actually do refer to you folks on here as "friends", with the common dream.
I think at some point on one train-ride home or another, we've searched for some sort of understanding and hope to know that we're not the only one. Today, I'm happy to know that my "friends" do share the same feeling at one point or another. And we are not alone.
