HNHacker News
TopNewBestAskShowJobs

iba99

470 karma · joined March 27, 2012

YC W'15: Tara AI is designed to help teams move faster in product development. Run weekly sprints and planned release cycles on-time.
submissionscomments
iba99··on Show HN: Tara – A free Jira alternative, now with Gitlab
Hey! So we had the option for a min char count, but users wanted to have one letter workspaces (for fun I guess?). We need to revamp our navigation anyway since it's hard to know where to click to change workspaces.

Good point on the whitespace- will take a look.

As for creating tasks- we're thinking of a sticky area on the left (that's always on) to create tasks.

For priority- we're releasing labels in 3 weeks. You should be able to assign #P1 or priority overall on different sets of tasks. That being said- we are considering adding some form of auto recognition or NLP to suggest priority and labels automatically based on past tasks. For time, we have 3 effort options (points, hours or days), we kept it simple to create a standup view where you can see how engineers track throughout the week.

Let us know which other parts may be tedious. We have more work to do!

iba99··on Show HN: Tara – A free Jira alternative, now with Gitlab
Hi HN! We last crossed paths 6 months ago, when we shared Tara 1.0, a simple Jira alternative. https://news.ycombinator.com/item?id=23033387

I'm one of the creators of Tara, and with support and feedback from the community, we've been hard at work building this v1.5 release over 24 sprints and 500+ pull requests. Several of you asked for an improved Github sync, PRs and commits tracked in tasks, alongside a Gitlab integration. We've discovered from teams, just how painful Jira and Confluence can be for tracking issues, sprints and docs. Our requirements feature has also gone through a bit of a re-design, and with Gitlab, we've also shipped commenting, workspaces and teams.

As for why we're working on this problem; we just wanted to use something fast, with minimal setup, and built-in views for Git. We just couldn't find anything designed from the ground up for development teams.

Finally, Tara AI is free for teams and developers. Our free forever plan has no limits on users, tasks or workspaces. Looking forward, we're working on predictive functionality around effort estimation, release planning and engineering analytics.

Thanks for reading!

iba99··on Show HN: Tara – A smart and free alternative to Jira
The key for our platform will always be simplicity. For now, the plan is to head into the technical side of software dev (Gitlab, Bitbucket and integrations with CI/CD tooling), without alienating business teams.

One of the biggest issues with existing PM software is that it's purpose built for singular teams, vs providing utility to cross-functional teams (e.g. engineering and growth). And it's usually overly complex with significant configuration required.

We're seeing early signs of this with requests from teams/orgs to add in marketing, growth and design teams as they need to be in the loop of releases and the overall SDLC.

iba99··on Show HN: Tara – A smart and free alternative to Jira
Ahh that's a cool idea- we really need to work on public sprint boards and actually show our weekly sprints and releases. We typically just discuss them on our twitter and our blog. Here's today's release: https://blog.tara.ai/release-log-may-1/
iba99··on Show HN: Tara – A smart and free alternative to Jira
What would be your biggest hurdle for adoption for a web-based version?
iba99··on Show HN: Tara – A smart and free alternative to Jira
Not yet - we're focusing on delivering other features related to task lifecycle, teams and integrations.
iba99··on Show HN: Tara – A smart and free alternative to Jira
Mosaic looks cool! Will give it a spin.
iba99··on Show HN: Tara – A smart and free alternative to Jira
We're releasing about two integrations per month (April was trello import and Github bi-directional sync) so we should get there soon! Our speed of shipping integrations is getting faster with time however.
iba99··on Show HN: Tara – A smart and free alternative to Jira
It's web-based.
iba99··on Show HN: Tara – A smart and free alternative to Jira
We actually need to update our about page - it still shows copy from our older version which was a predictions only product (I also talk about this below) with ref to a question asked about our .ai TLD.

We will be bringing our ML models back into the product for predictions over time. For now, we're really focusing on workflow and design as a platform.

iba99··on Show HN: Tara – A smart and free alternative to Jira
Yep. We still have some server latency- no optimistic loads just yet.
iba99··on Show HN: Tara – A smart and free alternative to Jira
Good ol' camtasia from my video editing days! Side hustled as a Udemy instructor in 2012, and camtasia is just as good now as it was back then.
iba99··on Show HN: Tara – A smart and free alternative to Jira
So internally, we're calling it the "task lifecycle". It's going to be a big feature, and the idea is to figure out the true development workflow (that works for 80% of users) and have statuses that update automatically based on Git. We're working on figuring out how to do this well enough, where the user doesn't have to go through complex configuration.
iba99··on Show HN: Tara – A smart and free alternative to Jira
Thanks! A few quick thoughts:

- We've done exactly this for Github <> Tara. We have a bi-directional sync with Github issues, and active issues are converted into tasks in Tara. Basically, if a user wanted to, they could just use Tara as a Github issue tracker.

- We wanted to start with Github, then work our way through more git/source control platforms, and then move to Jira. Interestingly, structuring incoming data from Jira requires a few months of work on data models IF we don't want the user to spend a ton of time labelling. Jira's data structure can be a hot mess to deal with.

- If the sync took a day or even a week of configuration, would you find it worth your time to invest and go through that? Or would yo expect the sync to work instantaneously (like Github <> Tara).

- What would be your expectations on mapping for histories?

iba99··on Show HN: Tara – A smart and free alternative to Jira
Sorry to hear! Can you elaborate on the issue?
iba99··on Show HN: Tara – A smart and free alternative to Jira
On it.
iba99··on Show HN: Tara – A smart and free alternative to Jira
Next on our roadmap!
iba99··on Show HN: Tara – A smart and free alternative to Jira
Any chance you can share a link to a screenshot and the console log? Appreciate it.
iba99··on Show HN: Tara – A smart and free alternative to Jira
So one thing we're working hard to do- is minimize the status updates required. For example- we built a simple home/dashboard where statuses can be updated with one click and individuals can focus on their priority tasks during the sprint.

We feel strongly about minimizing the amount of time spent wading through tickets and updating statuses. Currently working on a few other ideas/features that are related to status changes based on source control. Stay tuned.

As for power differential, the question is how do you instill a sense of camaraderie in individual engineers, and enable managers to load sprints with actual team data vs subjective measures. We're still working on improving this front - but so far - our "home" feature has been liked by both engineers and engineering managers.

iba99··on Show HN: Tara – A smart and free alternative to Jira
This. This is what we think about, constantly. How do we maintain the low to zero config teams ask for flexibility. We are a few apple engineers on the founding team (I'm not), and they really want to follow the approach set by Mac OS. Overall, Tara won't be for everyone, but it's a fine line between balancing the intuitive simple design and use case adjustments/workflows. Could be considered a matrix with several trade-offs.
iba99··on Show HN: Tara – A smart and free alternative to Jira
Good idea! We definitely need a pricing page to highlight the free forever plan.
iba99··on Show HN: Tara – A smart and free alternative to Jira
Not yet- it's otw!
iba99··on Show HN: Tara – A smart and free alternative to Jira
Painful and embarrassing is whenever I try to ride a bike.

A few quick thoughts on this:

- Jira started out as an issue tracker to monitor issues and tasks - it really wasn't built to handle software projects or the SDLC from the get go.

-Setting up insights and reporting can be a pain. And you need to be familiar with all the jargon (epics, stories, burn-down charts). Overall, it's a ton of cognitive overload.

-I used to just manage my issues on Github vs spending time configuring Jira. I only used Jira when the corporate overloads demanded it.

Here's the take on Tara vs Jira.

- We're zero to low config. There are entire 60 minute videos on youtube on how to setup sprints on Jira. On Tara, it's one click. We're really focusing on minimal functionality maximum impact in terms of matrix, and seeing how we can continue to be low config as we make the platform more powerful.

- Insights are ready and built- in with no setup. Once your github is connected, you can view commits and PRs by sprints

- We shipped our first smart indicator- it basically looks at your past few sprints (x>1 when x is no. of sprints) and tells you if your sprint has been overloaded. We're planning on shipping more smart indicators that make suggestions around effort, etc.

iba99··on Show HN: Tara – A smart and free alternative to Jira
Our first version (which failed miserably) was a prediction-only product with no workflow and a minimal interface. Here's what happened:

- Initially our hypothesis was we could build data models that automatically suggested a specification or tasks based on certain criteria the user identified (for e.g. iOS app for video based calling). - The system would suggest programming languages, frameworks and a set of tasks based on the criteria - User would immediately reject the suggestions/predictions outright (even if they were based collectively on data from stack overflow and other platforms). This would be due to a number of reasons: 1) Didn't trust the ML models to make the right predictions 2) The predictions were their first interaction with the platform.

As a result- we went back to the drawing board- and realized that to build a true "smart" project management system, we would need to start with intuitive workflows, and pepper in predictions over time based on usage and a team's actual stats. The AI tld stuck, plus we're planning on bringing the ML models to our public version soon. TBD.

We also plan on using NLP for automatic task connect to Git repos/PRs/commits and ML for predictions around effort estimates. But - we're still some time away from the open beta on making that a reality.

P.S. We recently acquired the tara.com domain which took 2 years of negotiations. A story for another time.

iba99··on Show HN: Tara – A smart and free alternative to Jira
Does a pandemic count? JK.

Frankly- RN we're more optimized for smaller teams. We lack the admin/user control and SAML functionality that Jira has for larger teams. It should be interesting to see if new teams about to on-board Jira cloud find the heavy config and long load times annoying and consider making the switch.

Majority of teams (for now) switch from Notion for sprints, Trello or Asana.

iba99··on Show HN: Tara – A smart and free alternative to Jira
Hey munkay- we're free for unlimited users. Principally, we believe teams shouldn’t have to be limited by user counts when deciding which project management system to use. Most are still clunky and cap at 10 users for free accounts- planning to have a free forever plan for unlimited users (much like Gitlab).

Paid plans may include functionality for enterprise teams, full fledged integrations and/or smart features such as automated sprint management.

As for Github auth- that's coming!

iba99··on Show HN: Tara – A smart and free alternative to Jira
Hey folks. My co-founder and I started noodling on productivity tools a few years ago. After interviewing 250+ engineers and founders, we discovered that most project management software a) takes a lot of time to configure b) is not built for cross-functional teams and c) takes away focus from the release cycle. The status quo is that engineers spend precious time wading through tickets, and EMs + PMs continue to lack visibility at the release level. This only gets worse with distributed teams across different time zones, and as teams outside of engineering rely on product to meet customer milestones and release dates.

Currently- the tool helps run and manage tasks, requirements and sprints. With team level insights and a smart indicator for sprint planning.

This is our open beta. RN Github integration is live for PRs and commits tied to sprints- we're still working on Bitbucket and Gitlab.

iba99··on Gradberry Spamming GitHub Users
Hi guys, founders here, we genuinely apologize to the community for for doing this. As a lesson to other founders and startups, here is exactly how it happened:

- Through github, we selected a total of 200 devs (13-14 from each repo that correlated with an open position)- based on their commits, prior experience, etc- If they seemed like the right fit for the position, we sent them an email.

It was a dumb decision, period. And we promise to never do this sort of thing again. Recruiter spam (or any other sort of spam) sucks, and we should have known better. Lesson learnt.

iba99··on Gradberry (YC W15) Curates Technical Talent
Hey guys, founder here, our team (in addition to our shortlisting algorithms) curates candidates through technical interviews by checking and verifying an engineer's github accounts and code repos- article was a tad unclear on the process. The human touch is just an add-on- through technical in-person interviews we are verifying that the automated process has not missed out on talent being shortlisted.

Think of it this way, we are aiming to find engineers that can immediately plug in to a company's code base as soon as they join, by verifying their current contributions on github.

(Full disclosure: we built recruiting software that hired for 1,500 companies prior to the current gradberry product). Happy to take any more of your questions! P.S. And yes we are focusing on the US market

iba99··on Curated + code-verified software engineering talent
Hey guys, founder here! Happy to field your questions. We moved out to Bay Area in January of this year, and are excited to be working with startups to curate and recommend software engineering talent. Here's how we envision the future of recruitment: 1- Curating talent based on actual work performed: i.e. with software engineering talent, our engineers are consistently checking code repositories on github for selected candidates, and we're building out algorithms that can actually decipher whether the candidate can plug in to a startup's code base as soon as they join. 2- Timed scenario-based challenges: Our challenges will identify the "ideal" candidate for the startup by assessing current employees at a startup, and timed scenarios determine how quickly a candidate can -write clean code or even -make cold calls and meet sales quotas. Our sales challenge has been able to accurately determine the likelihood of sales performance, and candidates achieving a score of 85% or higher have been able to achieve sales quotas. 3- Actual skills gap assessment: We're building out a trending skill engine (in beta), that determines which skills employers are consistently searching for. This allows us to advise a candidate exactly WHY they aren't getting hired. For e.g. C++ or Java developers who should consider learning Python or Ruby or Marketing graduate.
← PreviousPage 2 of 3Next →