It buys you what any API wrapper buys you: slightly increased developer velocity at the expense of occasional bugs that aren't in your code. Are you using python? Is your context that of a business that is attempting to trade engineering spend for bottom-line beats (or bottom-line improvements of any sort)? What is the project's timeline?
I don't think anyone can answer this for you, but if you'd like my personal opinion: use whatever delivers the most value in the least amount of time. On Fri, Aug 5, 2022, 1:19 PM David Early via users <[email protected]> wrote: > Hi all, > > Looking for opinion or experience on this one. > > I developed some basic nipyapi functions that got sidelined for a while. > Currently being picked up again but getting some questions about why we > should use nipyapi vs doing "direct" api queries without actually using the > api. > > It has been over a year since I did the initial work....i would like to > continue with the library vs direct, but was hoping for any experience or > opinions on why it would be good/bad to use nipyapi. What does it buy me? > > Thanks for any feedback, just looking to give some reasons to the young > guys coming in behind me. > > Dave > > -- > David Early, Ph.D. > [email protected] > 720-470-7460 Cell > >
