
Andy Powell
2.1K posts

Andy Powell
@apowellgt
Co-founder @ToolpathLabs & @CallRail. Lifelong entrepreneur.
Atlanta, GA Katılım Haziran 2008
164 Takip Edilen1.7K Takipçiler

@KennethCassel highly recommended. great fun. bought mine at 170k miles, sold it at 200k, missed it since 2007
English

@JonnyBird At this rate, they’ll be ground up and washed down the storm drain in two weeks. 😕
English

@NickPinkston @rob_lh @jack_watson_hfw I'm sorry to hear about this, and I hope there will be an opportunity to learn from their experience.
English

@rob_lh @jack_watson_hfw Market saturation is not what killed FormLogic, but I will defer to the team to post an after action report when they're ready and have thought it through.
In general, it's more this problem is very hard & complex both technically and operationally.
English

This sucks. FormLogic had some of the best technology in the CNC automation space that I've seen.
I wonder how the post ZIRP VC era will treat companies building deep tech in general.
AI is still in its mega hype period, but that will likely have a correction pretty soon.
Pittsburgh Startup News@pghstartupnews
SpaceX supplier @Formlogic closes Pittsburgh headquarters, cutting more than 40 tech jobs post-gazette.com/business/tech-… via @PittsburghPG
English

@zanehengsperger Love that he's all-in on toolpath automation. We're working to make this happen.
English

@Nico_Campolongo @istvan_csanady It's too soon to be certain, but in our initial testing it seems to be significantly faster and more reliable. We do need the actual contours rather than mesh-based approximations.
English

@apowellgt @istvan_csanady I can imagine how that quickly becomes slow and painful with OCCT 😅 is it better in terms of speed with Parasolid? Do you really need to do those operations with a CAD kernel though? Couldn’t you just mesh the part and use the mesh instead?
English

We need a CAD component provider to become the AWS of industrial software. The closest today is Siemens (Parasolid and DCM), but I think there is a huge opportunity to make it more successful. Why? Because CAD kernels are infrastructure, and they should be treated as such. The first kernel provider to realize this will dominate the market in the next decade. In this post, I’ll use Parasolid as an example, but the same applies to CGM, ACIS, and all high-end proprietary kernels. 👇
“Infrastructure | ˈɪnfrəˌstrʌktʃə |
The basic physical and organizational structures and facilities needed for the operation of a society or enterprise: the social and economic infrastructure of a country.”
Infrastructure is typically:
•Expensive, hard, and time-consuming to build.
•Very hard or impossible to replace without significant service interruptions.
•Provide a platform for a range of different services built on top of them (which also means that replacing them comes at the cost of replacing all services depending on them).
Parasolid checks all these boxes, but it behaves unlike the most successful software infrastructure providers. Here is what needs to change to ignite a new industrial software renaissance:
1. Make it more accessible
Today, starting a project based on Parasolid is not like starting a project on AWS. You need to negotiate a contract, explain your use case (which is usually unclear at the beginning of a new project), and go through their sales team—before you’ve made any money. This introduces enormous friction for launching a new project. The infrastructure of industrial software should be accessible at a very low cost until projects launch or monetize. In an ideal world, I should be able to pull a GitHub repository, start hacking a sample project, and have a working application an hour later.
2. Make it easier
Parasolid is fantastic, but it’s very low-level. To build an application, you need to write tens of thousands of lines of code just to get Parasolid off the ground. From memory management to graphics, there’s a ton of code that offers no competitive advantage, yet every company has to write it. This could be solved by making Parasolid more accessible and letting the community build this layer as open-source. There’s a wide talent pool eager to contribute to creating such a layer, and it’s a fun, collaborative project.
3. Make the documentation publicly available
The documentation should serve as a marketing tool for Parasolid. I don’t believe that the functional or API documentation of a software component provides any competitive advantage to anyone. By making it accessible to the developer community, it would act as an “appetizer” for enthusiastic engineers, inspiring them to build exciting new projects on top of Parasolid.
4. Build a community
Since the Parasolid ecosystem is currently closed, it’s impossible to build a vibrant community around it. A community would make it dramatically easier to build new applications on Parasolid, by providing support and developing a shared application layer.
5. Open-source as much as possible
This might sound scary or insane to some, but… I genuinely believe the value of Parasolid isn’t in its parts and algorithms, but in its role as the industry-standard infrastructure, creating a shared language between industrial applications. Making as much of it open-source as possible would engage developers further and increase trust in the platform. To be clear: I don’t think the licensing model should change. Parasolid should still charge for licenses, and I strongly believe forking should not be allowed to avoid diverging from standardization. However, some form of guarantee that customers could continue using the platform uninterrupted, even if something happens to Siemens PLM Components, would dramatically increase trust and likely attract more customers. I can even imagine a scenario where companies like Autodesk use Parasolid as their main kernel.
English

@Nico_Campolongo @istvan_csanady This will get beyond my knowledge, but our process slices the model many times and also projects many 3D curves onto planes. An error in a long chain of calls will break the analysis, and it needs to run autonomously -- the user doesn't have the chance to adjust and recover.
English

@istvan_csanady @apowellgt But interactive modeling and geometry analysis are 2 different use-cases. I believe that for geometry analysis the failure rate should be lower since you’re not modifying the part, just analyzing it. If you care about responsiveness/speed then sure
English

Visiting our friends, partners, and investors at @BobcatCompany in Fargo, ND. It really is the Google of North Dakota: incredible engineering, great product, deep expertise. Our @getgreenzie equipped autonomous mower will be at Equip Expo and it is looking good!
English

@ggraham As someone who enjoys projects and also wants to build a small barn, I'm intrigued. But compared to a professional crew, aren't most people (me included) negatively useful?
English


@zanehengsperger Thanks for stopping by @ToolpathLabs! Huge week showing off our software and building community.
English

@NickPinkston I'll be there all week, repping @ToolpathLabs in the machine hall. We've come a long way since IMTS 2022, come say hey!
English

ROLL CALL! Who's all going to IMTS next week?!?
This is the biggest manufacturing trade show in North America, and it only happens every other year.
If you're in Chicago, it's well worth a visit no matter who you are. Like a modern day World's Fair.
imts.com
GIF
English

@JonnyBird It's gorgeous, isn't it? I sent solid returns to investors from that teller line. Good times.
English

@mitchellh Is the second sim running now? What a great experience.
English

@KennethCassel I got my 10yo daughter a discovery flight in a 172 and I sat in the back seat. I was also interested in flying, and started flight lessons shortly after that flight.
English

@CollinMickels @Rollup Nice! We're fans of @JuliaLanguage at @ToolpathLabs. (Though we're more Glenn and less JPL.)
English

March 2009
I'd taken a consulting gig at Fortune 500 corporation in atlanta, running web analytics, paid search, lead gen ~ all that nonsense . I had just bought v1 iPhone & vividly remember taking these photos from my cubicle & thinking, "is this it? is this my view for the next 10-20-30 years?"
I had previously worked at web startups, and began to feel I preferred that level of semi-structured chaos.
but... but this was nice. ample pay. abundant healthcare. chefs prepping lunch every day. 2 hour lunch breaks.
something, though, that began to grate on me: buzzing-in with my badge every morning. the gate wouldn't open unless I did. a small reminder that I'm chattel. that they're tracking me. that I'm a number, and one step away from another layoff.
when my 6-month consulting gig concluded, they extended a hefty 6-figure salary to bring me on Full-time. it didn't take me long to reject that shit. my cubicle friends were dumbfounded. i didn't care.
I left & eventually ran into my old friend @roger_barnette who was building a new software startup, SearchIgnite, that served the growing paid search marketplace. "Holy shit, I know how to build this" I remember thinking. I essentially hounded him until he brought me on to continue building this (early) SaaS model aimed at AdWords, Overture, FindWhat, and the like (thank you again, Roger).
it was, while working there, that I began teaching myself how to code, how to build, how monetize websites, and most importantly (for me) how to discover expiring domain names.
sometimes these steps don't seem to make sense, until they do.



English

Damn, need to invent some Julia-appropriate work for myself now
Dr. Chris Rackauckas@ChrisRackauckas
#julialang v1.10 is released! Major "time to first X" and loading time improvements! With this one, I tend to not even do any system image shenanigans anymore: standard Julia is fast enough to start for me for anything I tend to use. Great work all! julialang.org/blog/2023/12/j…
English



















