|
I'm in the same boat, needing icons/graphics for a rebranding. As a small shop, I've done most of the graphics/icons for the last 20 years, building on a set that we had done professionally. For new projects, I've usually found stuff that works on the web, or at least close enough that is just requires resizing/recoloring in Paint. (or even using the old MS Photo Editor) I tried using Gimp but it crashed so much that it didn't make the cut on the new system...I'm really thinking about an Adobe (probably Illustrator) subscription to see what it can do. Ideally, we could spend some money and hire a local ad agency and I could concentrate on code! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
If you have a graphics tablet or the $80 or so to spend on one, Krita[^] is free. I've been using it for the last few weeks to practice on my computer graphics. It's got some annoying quirks but I'm still learning the software.
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|
|
|
I can be pretty graphic, but I'm not much of an artist.
We used to have a Jobs board here, just for the purpose of connecting users with competent providers, but I haven't seen it in a while. Perhaps you should try Google, or LinkedIn services.
Will Rogers never met me.
|
|
|
|
|
I'm pretty graphic, but I am certainly no artist.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
I have two sons that do graphics, although they are more focused on video games and anime. They might be willing for a reasonable fee.
Money makes the world go round ... but documentation moves the money.
|
|
|
|
|
State of affairs (this is with TFS, Git is not used):
- All projects, regardless of how unrelated, are in a single SLN
- When releasing to production, changesets have to be cherry picked for "just the changes being released" for the different projects.
- After merge to prod, the SLN file has to be visually / manually compared and edited to remove projects that might have been added that shouldn't be going to prod.
- The branching policy stands as: "branches are too complicated"
- The check-in policy stands as: "to avoid tons of work for a release, do NOT check in frequently, so that there's ideally only one changeset for the last 3 months of work."
Umm. What's wrong with this picture? 
|
|
|
|
|
Marc Clifton wrote: What's wrong with this picture?
TFS! You are using TFS!
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
We use TFS for a huge solution and it is fine if it is setup and used properly.
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
TFS is not the problem. The same policies would still exist if using Github or another tool. The problem is how TFS is being used.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
All that crap and manual work and they say its the whole BRANCH thing is too complicated. 
|
|
|
|
|
Well, branching on TFS does suck. That's probably GIT's primary advantage over TFS. (GIT's distributed nature is useful is a massive diverse project like Linux, but of really little use in most places)
Truth,
James
|
|
|
|
|
1. Not good
2. Use labels
3. See 1
4. I've never used branches either, but I try to avoid worse things
5. See 2
|
|
|
|
|
Marc Clifton wrote: Umm. What's wrong with this picture?
1. - makes the possibility of CI pretty much impossible.
2. - see 1.
3. - see 1.
4. - people need more training.
5. - irrelevance, the number of checkins has no bearing on the validity of trunk -> if your check in breaks trunk you fix it or revert out your changes.
Source control done properly is certainly not easy but what you have listed is just as complicated, if not more complicated, as doing source control properly.
In addition to 4. - trunk based development is a perfectly valid and at times necessary method of development if you want to be able to deploy at any time when the tests all show green. Branch based development is not necessarily complicated and has its own advantages such as no breaking trunk if you are deploying from trunk.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 12-Jul-18 12:59pm.
|
|
|
|
|
GuyThiebaut wrote: 1. - makes the possibility of CI pretty much impossible.
Precisely! If I mention CI around here, I get blank stares or "did you mean the TV show CSI?"
|
|
|
|
|
There are people with intellects far superior to mine who struggle with implementing CI.
It's a long process to get there and I can only claim to understand some of the principles.
However, even if CI is not the end goal, having everything in one solution is really not a very good idea nowadays given all the tools(Nuget etc) and experience documented on how to reduce risk and do things 'properly'.
Your post also makes me grateful that I work somewhere that has fairly decent source control practises - that said it took me a good 6 months to really absorb how to do source control properly - using project branches, a trunk, release candidate branches etc.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Umm. Everything?
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Let me guess: this is also the official backup system for the company?
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: this is also the official backup system for the company?
Actually no - that seems to be handled fairly well.
|
|
|
|
|
Easier question : what's right about it?
|
|
|
|
|
Sounds to me like this is the wrong company to be working for. I am sure they are not going to change their ways anytime soon.
|
|
|
|
|
I could've launched into a long diatribe, but I'll summarize it much more succinctly:
The incompetence of the individual(s) in charge is harmful to everybody else.
There. Is there really much else to add?
|
|
|
|
|
There's a word for that
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Marc Clifton wrote: a single SLN
Marc Clifton wrote: Umm. What's wrong with this picture?
Always use married SLNs they are more stable and reliable. 
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Heart | [heart]](https://www.codeproject.com/script/Forums/Images/love.gif)
the free (for commercial use) icons at 
