BigBad thieving

Freshness Warning
This blog post is over 19 years old. It's possible that the information you read below isn't current and the links no longer work.

Almost a year ago I mentioned that Boston-based Web development firm BigBad was presenting some of my work (and the work of others) as their own. Worse, they were using the stolen work as an example of the cutting edge development they were doing.

I said…

I’m willing to give the company the benefit of the doubt. Elsewhere on their site, the code is credited to “Tim Seit, Applications Developer, BigBad.” Perhaps Mr. Seit didn’t tell his employers that he didn’t actually write any of that code. BigBad may be blissfully unaware of this mis-step.

Tonight Tim Seit contacted me by IM and apologized. He no longer works at BigBad and stumbled across my article when searching on his name. Tim said “when I came across the code I presented it to my manager as code that I came across during a Google search, not something that I had written. BigBad was made fully aware that I made no original contributions to that code.”

So apparently the management at BigBad knew they didn’t write the code but decided to take credit for it anyway, despite the objections of their developers.

March 21, 2004 7:54 AM

This is somthing that really irritates and irks, Law suit comes to mind and also big company bully which is something that we are investigating at the moment,You know who you are!

February 22, 2005 10:44 AM

What's interesting is that they haven't taken it down yet - given that this page is the #3 result on Google for the word 'bigbad'.

Darren Mauro
April 1, 2005 10:48 AM

As fellow software developers, we appreciate Mr. Kalsey's concerns over proper attribution for intellectual property. As Mr. Kalsey points out, a number of the WebToys on our site leverage code or algorithms developed by third parties. In each case, the third party contribution was a code sample made freely available on the Web and its developer has encouraged and suggested reuse of the code. However, since this issue has come to our attention (not directly from Mr. Kalsey but through a third party), we have reviewed the way that each of these is presented. While our review determined that there was no intent to misrepresent who was responsible for which portions of the work, we have also identified that some of the WebToys did not completely adhere to the original developer's request for how the code was credited or could benefit from more visible attribution where third-party code was leveraged. We have made updates to each of the three WebToys mentioned that leverage the work of third parties to clearly indicate this in prominent positions within each application as well as in code comments, according to the specific requests of each original developer. While some of the WebToys contain reused code, we believe that each WebToy represents a unique product of BigBad's concept for how the third-party element combined with original visual design, theme/message, and often additional new code can together provide an entertaining example of the power of the Web to engage, entertain, and inform. This was our intention all along and we have attempted to clarify this purpose on the WebToys page as well. If any of the original developers feel that their contributions have not been properly represented, we welcome a direct dialogue with the concerned party, as this is more likely to achieve a mutually acceptable resolution more quickly than an indirect forum like this one. BigBad

Adam Kalsey
April 1, 2005 11:10 AM

Of course my initial email requesting that the problem be taken care of went unanswered two years ago when I sent it. But once a search for "BigBad" started turning up negative results, then something needed to be done about it, right?

Mark Heverstein
February 21, 2010 8:21 AM

I was browsing around, considering using BigBad for a Higher Ed project I have. However after reading this and a bunch of other poor reviews (i.e. paper pushers, a project-management company: no creative or technical skills, etc), BigBad had gone to the bottom of my list. BigBad -- you're a big bad company, we don't need companies like you around.

Art Director
February 14, 2012 2:47 PM

Even though BigBad is now gone (as a result of mismanagment and illegal activities by its CEO ... Googling will easily provide more detail on this), I must take issue with Mr. Heverstein's comment above. As a former employee, I can support your decision not to go with BigBad in an early 2010 timeframe--at this point mismanagement had taken its toll, employees were not being paid, and the company was circling the drain. But to say that the creative staff at BigBad was anything but top-notch is both inaccurate and unfounded. The team there had a solid record and reputation for creating excellent, award-winning solutions which met client and user needs while also advancing brand, and was well known and well regarded nationally in the Higher Ed space.

This discussion has been closed.

Recently Written

The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2023 Adam Kalsey.