C++ coder required

Hi

I am a complete novice when it comes to coding so I have a team that helps
me design vstis for the audio industry.

We have a coder but are not confident in his abilities as he doesn't seem
to understand maths and we tech heads talk in maths. He doesn't seem to
grasp schematics either and is not English so explaining simple
rudimentary functions can take ages.

We are tightly linked to Sound On Sound magazine and this vsti has been in
the making for 3 years as it incorporates advanced technologies.

We are looking for a coder to undertake either helping our coder with DSP
algorithms or to recode the whole project. 

Please feel free to contact me directly at:

info_at_samplecraze.com

Many thanks.

Eddie Bazil
Samplecraze


---------------------------------------
Posted through http://www.DSPRelated.com

On 20/01/16 15:09, zukan wrote:
> Hi
>
> I am a complete novice when it comes to coding so I have a team that helps
> me design vstis for the audio industry.
>
> We have a coder but are not confident in his abilities as he doesn't seem
> to understand maths and we tech heads talk in maths. He doesn't seem to
> grasp schematics either and is not English so explaining simple
> rudimentary functions can take ages.
>
> We are tightly linked to Sound On Sound magazine and this vsti has been in
> the making for 3 years as it incorporates advanced technologies.
>
> We are looking for a coder to undertake either helping our coder with DSP
> algorithms or to recode the whole project.
>
> Please feel free to contact me directly at:
>
> info_at_samplecraze.com
>
> Many thanks.
>
> Eddie Bazil
> Samplecraze

It would help if you outlined the runtime environment and
how much you are paying.

On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:

> Hi
> 
> I am a complete novice when it comes to coding so I have a team that
> helps me design vstis for the audio industry.
> 
> We have a coder but are not confident in his abilities as he doesn't
> seem to understand maths and we tech heads talk in maths. He doesn't
> seem to grasp schematics either and is not English so explaining simple
> rudimentary functions can take ages.
> 
> We are tightly linked to Sound On Sound magazine and this vsti has been
> in the making for 3 years as it incorporates advanced technologies.
> 
> We are looking for a coder to undertake either helping our coder with
> DSP algorithms or to recode the whole project.
> 
> Please feel free to contact me directly at:
> 
> info_at_samplecraze.com
> 
> Many thanks.
> 
> Eddie Bazil Samplecraze

First: feel free to contact me by email, I may be interested.

Second: there's a lot of advantage to someone local, so you may not be 
interested in me.

Third: With all due respect, this sounds like a failure in interviewing 
and job specification.  If you're not pissed off by that comment, here 
are some suggestions:

1: Advertise for a software engineer, not a "coder".  A "coder" is a 
person who cobbles code together.  An engineer is a person who does 
structured design of the entire software set, and even (in embedded 
projects) impacts the hardware design.  Do you want a rotting pile of 
spaghetti code, or do you want software?

2: Interview for the skills you need.  You needed someone who speaks 
fluent English and reads schematics -- you should interview for this, in 
addition to being a good software engineer.

3: Expect to get what you pay for.  It sounds like you hired a budget 
guy, and now you're enjoying the fruits of your "savings".  

4: Hire what you need. Judging from what little I can glean from your 
post, you need someone who, around here, would be considered an Engineer 
III or Engineer IV -- basically, you want someone who can do medium-sized 
projects entirely independently, or even be able to supervise lower-level 
engineers.  It sounds like what you have is an Engineer I (wet behind the 
ears college kid) or Engineer II (one or two years of experience, or 
someone with limited initiative and/or ability).

If this were a full-time position and you were local to me, I would 
suggest that if you didn't want to hire me for the job, that you might 
consider hiring me as a consultant to help you vet your candidates.  I 
could do this, but once again I think someone local to you would be 
better.  Get someone with at least a decade of experience to spend 
several hours talking to you about what you need, and then help you hire 
someone with three or more years of experience.

I _may_ be able to dig up a name for you for consultant in Bucks, but if 
I have it at all it's buried in some really old correspondence.  I can't 
guarantee anything, but email me if you're interested.

5: Don't be afraid to hire an older person.  I don't know how old you are 
or your prejudices, but in a lot of countries people who just want to be 
technical contributors tend to have trouble keeping their jobs at bigger 
companies once they start showing gray in their hair.  Yet, such people 
can bring a great deal of wisdom and experience to a job.  Since you're a 
small company you need to be flexible to compete with big companies -- 
consider this a suggestion as to a direction to flex.

-- 

Tim Wescott
Wescott Design Services
http://www.wescottdesign.com

>On 20/01/16 15:09, zukan wrote:
>> Hi
>>
>> I am a complete novice when it comes to coding so I have a team that
>helps
>> me design vstis for the audio industry.
>>
>> We have a coder but are not confident in his abilities as he doesn't
seem
>> to understand maths and we tech heads talk in maths. He doesn't seem
to
>> grasp schematics either and is not English so explaining simple
>> rudimentary functions can take ages.
>>
>> We are tightly linked to Sound On Sound magazine and this vsti has
been
>in
>> the making for 3 years as it incorporates advanced technologies.
>>
>> We are looking for a coder to undertake either helping our coder with
DSP
>> algorithms or to recode the whole project.
>>
>> Please feel free to contact me directly at:
>>
>> info_at_samplecraze.com
>>
>> Many thanks.
>>
>> Eddie Bazil
>> Samplecraze
>
>It would help if you outlined the runtime environment and
>how much you are paying.

Will do Tom. We are waiting to finalise the scope of the project.
---------------------------------------
Posted through http://www.DSPRelated.com

>On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
>
>> Hi
>> 
>> I am a complete novice when it comes to coding so I have a team that
>> helps me design vstis for the audio industry.
>> 
>> We have a coder but are not confident in his abilities as he doesn't
>> seem to understand maths and we tech heads talk in maths. He doesn't
>> seem to grasp schematics either and is not English so explaining
simple
>> rudimentary functions can take ages.
>> 
>> We are tightly linked to Sound On Sound magazine and this vsti has
been
>> in the making for 3 years as it incorporates advanced technologies.
>> 
>> We are looking for a coder to undertake either helping our coder with
>> DSP algorithms or to recode the whole project.
>> 
>> Please feel free to contact me directly at:
>> 
>> info_at_samplecraze.com
>> 
>> Many thanks.
>> 
>> Eddie Bazil Samplecraze
>
>First: feel free to contact me by email, I may be interested.
>
>Second: there's a lot of advantage to someone local, so you may not be 
>interested in me.
>
>Third: With all due respect, this sounds like a failure in interviewing 
>and job specification.  If you're not pissed off by that comment, here 
>are some suggestions:
>
>1: Advertise for a software engineer, not a "coder".  A "coder" is a 
>person who cobbles code together.  An engineer is a person who does 
>structured design of the entire software set, and even (in embedded 
>projects) impacts the hardware design.  Do you want a rotting pile of 
>spaghetti code, or do you want software?
>
>2: Interview for the skills you need.  You needed someone who speaks 
>fluent English and reads schematics -- you should interview for this, in

>addition to being a good software engineer.
>
>3: Expect to get what you pay for.  It sounds like you hired a budget 
>guy, and now you're enjoying the fruits of your "savings".  
>
>4: Hire what you need. Judging from what little I can glean from your 
>post, you need someone who, around here, would be considered an Engineer

>III or Engineer IV -- basically, you want someone who can do medium-sized

>projects entirely independently, or even be able to supervise lower-level

>engineers.  It sounds like what you have is an Engineer I (wet behind the

>ears college kid) or Engineer II (one or two years of experience, or 
>someone with limited initiative and/or ability).
>
>If this were a full-time position and you were local to me, I would 
>suggest that if you didn't want to hire me for the job, that you might 
>consider hiring me as a consultant to help you vet your candidates.  I 
>could do this, but once again I think someone local to you would be 
>better.  Get someone with at least a decade of experience to spend 
>several hours talking to you about what you need, and then help you hire

>someone with three or more years of experience.
>
>I _may_ be able to dig up a name for you for consultant in Bucks, but if

>I have it at all it's buried in some really old correspondence.  I can't

>guarantee anything, but email me if you're interested.
>
>5: Don't be afraid to hire an older person.  I don't know how old you are

>or your prejudices, but in a lot of countries people who just want to be

>technical contributors tend to have trouble keeping their jobs at bigger

>companies once they start showing gray in their hair.  Yet, such people 
>can bring a great deal of wisdom and experience to a job.  Since you're a

>small company you need to be flexible to compete with big companies -- 
>consider this a suggestion as to a direction to flex.
>
>-- 
>
>Tim Wescott
>Wescott Design Services
>http://www.wescottdesign.com


Tim, that's wonderful advice. Truly indebted.

The problem is/was that I am the signal path designer and the employment
of a coder is left to the team to agree upon and our coder came on
recommendation.

He preferred a share in the product as opposed to money as he wanted to be
involved in this particular project. 
This was better for us as it meant we would have an in-house coder which
we could utilise on forthcoming projects.
---------------------------------------
Posted through http://www.DSPRelated.com

Just curious. If you replace him does he keep his share in the project?

Dirk


On Thursday, January 21, 2016 at 9:51:08 AM UTC-5, zukan wrote:
> >On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
> >
> >> Hi
> >> 
> >> I am a complete novice when it comes to coding so I have a team that
> >> helps me design vstis for the audio industry.
> >> 
> >> We have a coder but are not confident in his abilities as he doesn't
> >> seem to understand maths and we tech heads talk in maths. He doesn't
> >> seem to grasp schematics either and is not English so explaining
> simple
> >> rudimentary functions can take ages.
> >> 
> >> We are tightly linked to Sound On Sound magazine and this vsti has
> been
> >> in the making for 3 years as it incorporates advanced technologies.
> >> 
> >> We are looking for a coder to undertake either helping our coder with
> >> DSP algorithms or to recode the whole project.
> >> 
> >> Please feel free to contact me directly at:
> >> 
> >> info_at_samplecraze.com
> >> 
> >> Many thanks.
> >> 
> >> Eddie Bazil Samplecraze
> >
> >First: feel free to contact me by email, I may be interested.
> >
> >Second: there's a lot of advantage to someone local, so you may not be 
> >interested in me.
> >
> >Third: With all due respect, this sounds like a failure in interviewing 
> >and job specification.  If you're not pissed off by that comment, here 
> >are some suggestions:
> >
> >1: Advertise for a software engineer, not a "coder".  A "coder" is a 
> >person who cobbles code together.  An engineer is a person who does 
> >structured design of the entire software set, and even (in embedded 
> >projects) impacts the hardware design.  Do you want a rotting pile of 
> >spaghetti code, or do you want software?
> >
> >2: Interview for the skills you need.  You needed someone who speaks 
> >fluent English and reads schematics -- you should interview for this, in
> 
> >addition to being a good software engineer.
> >
> >3: Expect to get what you pay for.  It sounds like you hired a budget 
> >guy, and now you're enjoying the fruits of your "savings".  
> >
> >4: Hire what you need. Judging from what little I can glean from your 
> >post, you need someone who, around here, would be considered an Engineer
> 
> >III or Engineer IV -- basically, you want someone who can do medium-sized
> 
> >projects entirely independently, or even be able to supervise lower-level
> 
> >engineers.  It sounds like what you have is an Engineer I (wet behind the
> 
> >ears college kid) or Engineer II (one or two years of experience, or 
> >someone with limited initiative and/or ability).
> >
> >If this were a full-time position and you were local to me, I would 
> >suggest that if you didn't want to hire me for the job, that you might 
> >consider hiring me as a consultant to help you vet your candidates.  I 
> >could do this, but once again I think someone local to you would be 
> >better.  Get someone with at least a decade of experience to spend 
> >several hours talking to you about what you need, and then help you hire
> 
> >someone with three or more years of experience.
> >
> >I _may_ be able to dig up a name for you for consultant in Bucks, but if
> 
> >I have it at all it's buried in some really old correspondence.  I can't
> 
> >guarantee anything, but email me if you're interested.
> >
> >5: Don't be afraid to hire an older person.  I don't know how old you are
> 
> >or your prejudices, but in a lot of countries people who just want to be
> 
> >technical contributors tend to have trouble keeping their jobs at bigger
> 
> >companies once they start showing gray in their hair.  Yet, such people 
> >can bring a great deal of wisdom and experience to a job.  Since you're a
> 
> >small company you need to be flexible to compete with big companies -- 
> >consider this a suggestion as to a direction to flex.
> >
> >-- 
> >
> >Tim Wescott
> >Wescott Design Services
> >http://www.wescottdesign.com
> 
> 
> Tim, that's wonderful advice. Truly indebted.
> 
> The problem is/was that I am the signal path designer and the employment
> of a coder is left to the team to agree upon and our coder came on
> recommendation.
> 
> He preferred a share in the product as opposed to money as he wanted to be
> involved in this particular project. 
> This was better for us as it meant we would have an in-house coder which
> we could utilise on forthcoming projects.
> ---------------------------------------
> Posted through http://www.DSPRelated.com

On Thursday, January 21, 2016 at 2:44:26 PM UTC-5, belld...@gmail.com wrote:
> Just curious. If you replace him does he keep his share in the project?
> 
> Dirk
> 
> 
> On Thursday, January 21, 2016 at 9:51:08 AM UTC-5, zukan wrote:
> > >On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
> > >
> > >> Hi
> > >> 
> > >> I am a complete novice when it comes to coding so I have a team that
> > >> helps me design vstis for the audio industry.
> > >> 
> > >> We have a coder but are not confident in his abilities as he doesn't
> > >> seem to understand maths and we tech heads talk in maths. He doesn't
> > >> seem to grasp schematics either and is not English so explaining
> > simple
> > >> rudimentary functions can take ages.
> > >> 
> > >> We are tightly linked to Sound On Sound magazine and this vsti has
> > been
> > >> in the making for 3 years as it incorporates advanced technologies.
> > >> 
> > >> We are looking for a coder to undertake either helping our coder with
> > >> DSP algorithms or to recode the whole project.
> > >> 
> > >> Please feel free to contact me directly at:
> > >> 
> > >> info_at_samplecraze.com
> > >> 
> > >> Many thanks.
> > >> 
> > >> Eddie Bazil Samplecraze
> > >
> > >First: feel free to contact me by email, I may be interested.
> > >
> > >Second: there's a lot of advantage to someone local, so you may not be 
> > >interested in me.
> > >
> > >Third: With all due respect, this sounds like a failure in interviewing 
> > >and job specification.  If you're not pissed off by that comment, here 
> > >are some suggestions:
> > >
> > >1: Advertise for a software engineer, not a "coder".  A "coder" is a 
> > >person who cobbles code together.  An engineer is a person who does 
> > >structured design of the entire software set, and even (in embedded 
> > >projects) impacts the hardware design.  Do you want a rotting pile of 
> > >spaghetti code, or do you want software?
> > >
> > >2: Interview for the skills you need.  You needed someone who speaks 
> > >fluent English and reads schematics -- you should interview for this, in
> > 
> > >addition to being a good software engineer.
> > >
> > >3: Expect to get what you pay for.  It sounds like you hired a budget 
> > >guy, and now you're enjoying the fruits of your "savings".  
> > >
> > >4: Hire what you need. Judging from what little I can glean from your 
> > >post, you need someone who, around here, would be considered an Engineer
> > 
> > >III or Engineer IV -- basically, you want someone who can do medium-sized
> > 
> > >projects entirely independently, or even be able to supervise lower-level
> > 
> > >engineers.  It sounds like what you have is an Engineer I (wet behind the
> > 
> > >ears college kid) or Engineer II (one or two years of experience, or 
> > >someone with limited initiative and/or ability).
> > >
> > >If this were a full-time position and you were local to me, I would 
> > >suggest that if you didn't want to hire me for the job, that you might 
> > >consider hiring me as a consultant to help you vet your candidates.  I 
> > >could do this, but once again I think someone local to you would be 
> > >better.  Get someone with at least a decade of experience to spend 
> > >several hours talking to you about what you need, and then help you hire
> > 
> > >someone with three or more years of experience.
> > >
> > >I _may_ be able to dig up a name for you for consultant in Bucks, but if
> > 
> > >I have it at all it's buried in some really old correspondence.  I can't
> > 
> > >guarantee anything, but email me if you're interested.
> > >
> > >5: Don't be afraid to hire an older person.  I don't know how old you are
> > 
> > >or your prejudices, but in a lot of countries people who just want to be
> > 
> > >technical contributors tend to have trouble keeping their jobs at bigger
> > 
> > >companies once they start showing gray in their hair.  Yet, such people 
> > >can bring a great deal of wisdom and experience to a job.  Since you're a
> > 
> > >small company you need to be flexible to compete with big companies -- 
> > >consider this a suggestion as to a direction to flex.
> > >
> > >-- 
> > >
> > >Tim Wescott
> > >Wescott Design Services
> > >http://www.wescottdesign.com
> > 
> > 
> > Tim, that's wonderful advice. Truly indebted.
> > 
> > The problem is/was that I am the signal path designer and the employment
> > of a coder is left to the team to agree upon and our coder came on
> > recommendation.
> > 
> > He preferred a share in the product as opposed to money as he wanted to be
> > involved in this particular project. 
> > This was better for us as it meant we would have an in-house coder which
> > we could utilise on forthcoming projects.
> > ---------------------------------------
> > Posted through http://www.DSPRelated.com

"Just curious. If you replace him does he keep his share in the project?"

really stupid question... of course he does

- By keeping copies of all of the design documentation provided to him and all of the code developed up to date for himself :):):)

On Thursday, January 21, 2016 at 8:51:08 AM UTC-6, zukan wrote:
> >On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
> He preferred a share in the product as opposed to money as he wanted to be
> involved in this particular project. 

There's your real problem. In fact, the first thing I would have asked is: shared royalties? (and in reply to "No", "Then you're my competition ... and I take no prisoners.").

A lot of programmers, I think, are wising up to the traditional contract-for-hire arrangement. You see: it's a lot of brain-busting creativity to put into something that is -- in effect -- a form of authoring and writing (not engineering; yes, I'm talking to you, fellow DSP'ers!) and to have the fruits of one's creativity go out to someone else with nothing to show for it but some money, is way too much to lose.

It's a lot like slicing off layers of your brain to give to someone else as a brain transplant donor.

If you do the following you may get more takers: (1) ensure the actual coding be distributable and distributed open source, (2) contract only for the fitting of the code to the application on hand (the widget) -- which qualifies as a service analogous to being an editor, rather than a form of writing or engineering, (3) keep the original developers' names on the code, copyrighting it in their names (but to be distributed under copyleft).

Better yet, look for freely distributed DSP libraries that do VST, take them and adapt them to your projects.

Either way, in the process, you'll also make your operation more Millennial-friendly in appearance, rather than something more reminiscent of the Sears, McDonalds, Walmarts, Microsofts of the world and the previous century.

On Thursday, January 21, 2016 at 5:59:14 PM UTC-5, federat...@netzero.com wrote:
> On Thursday, January 21, 2016 at 8:51:08 AM UTC-6, zukan wrote:
> > >On Wed, 20 Jan 2016 09:09:05 -0600, zukan wrote:
> > He preferred a share in the product as opposed to money as he wanted to be
> > involved in this particular project. 
> 
> There's your real problem. In fact, the first thing I would have asked is: shared royalties? (and in reply to "No", "Then you're my competition ... and I take no prisoners.").
> 
> A lot of programmers, I think, are wising up to the traditional contract-for-hire arrangement. You see: it's a lot of brain-busting creativity to put into something that is -- in effect -- a form of authoring and writing (not engineering; yes, I'm talking to you, fellow DSP'ers!) and to have the fruits of one's creativity go out to someone else with nothing to show for it but some money, is way too much to lose.
> 
> It's a lot like slicing off layers of your brain to give to someone else as a brain transplant donor.
> 
> If you do the following you may get more takers: (1) ensure the actual coding be distributable and distributed open source, (2) contract only for the fitting of the code to the application on hand (the widget) -- which qualifies as a service analogous to being an editor, rather than a form of writing or engineering, (3) keep the original developers' names on the code, copyrighting it in their names (but to be distributed under copyleft).
> 
> Better yet, look for freely distributed DSP libraries that do VST, take them and adapt them to your projects.
> 
> Either way, in the process, you'll also make your operation more Millennial-friendly in appearance, rather than something more reminiscent of the Sears, McDonalds, Walmarts, Microsofts of the world and the previous century.

 "...ensure the actual coding be distributable and distributed open source" ???
What ???

And how is the company going to make money on their product which is some kind of advanced VST plugin from his description ???

Some of those commercial VST plugin developers use USB dongles to prevent crackers from stealing their precious (compiled) code, cause software-only based licensing protection mechanism doesn't work too well...

But then USB dongles suck so much that a lot of even legitimate software users prefer cracked copies pf their favorite software to legal originals - much easier to install and use on different computers

As for the "pride of programmers" - pitch this crap to young romantic (aka stupid and naive) dudes, and even those are hard to find nowadays

Older dudes with families and bills to pay will (almost) always take money instead, but real money justifying time and effort, not some symbolic amount   

<federation2005@netzero.com> wrote:

>A lot of programmers, I think, are wising up to the traditional
>contract-for-hire arrangement. You see: it's a lot of brain-busting
>creativity to put into something that is -- in effect -- a form of
>authoring and writing (not engineering; yes, I'm talking to you, fellow
>DSP'ers!) and to have the fruits of one's creativity go out to someone
>else with nothing to show for it but some money, is way too much to
>lose.
>
>It's a lot like slicing off layers of your brain to give to someone else
>as a brain transplant donor.

Each contract is different.  There really is no such thing
as a "traditional contact-for-hire" arrangement, because each
arrangement is at least somewhat different from the others, and
traditions such as they exist mutate pretty rapidly.  A 
successful worker, whether contractor or employee, signs up for 
work they are overall comfortable performing, even if it is challenging
and/or time-consuming.  

Steve