Figuring out what I want to do

One of the things I've wrestled with in the past is whether or not I want to start a little photography business. This would obviously be something on the side where I shoot after work or on weekends. I almost got going a few years ago but never quite pulled the trigger. I did a senior photos shoot for a neighbor and they loved the results, or so they told me :). I thought that would get me started but I never put any effort into getting more business. Here I am a couple of years later with a renewed spirit for taking photos and that question popped into my mind again. The big reason it did was that I used a friends 28-70 f/2.8 lens this fall and loved how the photos looked. I decided I wanted one for myself. Well, if I'm going to spend that kind of money then I should try to make some money as well right? For me, the answer is wrong. I just don't want to give up my free time to take photos for someone else, then process them, then print them, then meet with the person to give them there photos and wrap up. I want to spend the bulk of my time just shooting and other stuff that really interests me, like fishing and playing soccer. So I've decided this will always just be a hobby for me, an expensive one :). I'm sure I'll do my own kids senior photos and occasionally do a shoot for someone if they ask but I'm definitely not going to market myself and try to turn it into a business. In my gut this feels like the right decision and has for a couple of weeks now.

Comments

Post a Comment

Popular posts from this blog

Database, schema, and table sizes in Greenplum

Starting in the 4.x release, you get size info from the gp_toolkit schema. To get the size of all databases and their size in bytes: select sodddatname, sodddatasize from gp_toolkit.gp_size_database; To see the database size in GB, TB, and/or MB. TB: select sodddatname, (sodddatsize/1073741824)/1024 AS sizeinTB from gp_toolkit.gp_size_of_database; GB: select sodddatname, (sodddatsize/1073741824) AS sizeinGB from gp_toolkit.gp_size_of_database; MB: select sodddatname, (sodddatsize/1048576) AS sizeinMB from gp_toolkit.gp_size_of_database; For schema sizes , connect to your database and run: TB: select sosdnsp, (sosdschematablesize/1073741824)/1024 AS schemasizeinTB from gp_toolkit.gp_size_of_schema_disk; GB: select sosdnsp, (sosdschematablesize/1073741824) AS schemasizeinGB from gp_toolkit.gp_size_of_schema_disk; MB: select sosdnsp, (sosdschematablesize/1048576) AS schemasizeinMB from gp_toolkit.gp_size_of_schema_disk; If you want a specific schema only, add
Read more

Greenplum update with multiple tables

Recently ran into an issue using Greenplum to update a column. I had column1 in tableA that needed to be set to the value of column1 in tableB. Finally came across the correct syntax here . This is what I was looking for: UPDATE tableA  SET col1 = tableB.col1  FROM tableB  WHERE tableA.col2=tableB.col2;
Read more

Show running queries on Postgresql/Greenplum

I've got some queries that run for a long time. Sometimes longer than others. I wanted to see how long active queries have been running. Here's a view to consistently do that: CREATE VIEW public.view_activequeries AS ( SELECT age(query_start, backend_start) AS queryage,* FROM pg_stat_activity WHERE current_query NOT LIKE '%IDLE%' ORDER BY queryage DESC); Then you just run: select * from public.view_activequeries; You get a list of all active queries in descending order of how long they have been running, i.e. longest running queries listed first.
Read more