Earlier quoted context omitted.
useState is a memoization technique and an abstraction to hide global state. You can do: let _count = 0; function Component() { return ( {_count} { _count++; render(); }}>Increase ); } function render() { React.render( , root) } Or you can abstract it: let _count; function useCount(initialValue) { return [_count, (value) => { _count = value; render(); }] } function Component() { const [count, setCount] = useCount(0);…
For a developer who has not done React before - this looks super convoluted for some reason. Global functions with constants defined in another function, that act as ... methods? I'm lost :D
A Simplified Jira Clone Built with React/Babel and Node/TypeScript
71–80 of 101 posts
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#72We are building a new issue tracker for software teams. https://linear.app
Especially making the UX feel fast, we since the slowness is really annoying in software that you use daily. The app built more like native client, caching the data locally and syncing the transactions the the background. That way it also supports offline use.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#73Earlier quoted context omitted.
Fewer features sounds great. I personally loath Jira, and avoid using it whenever possible, but your clone looks really nice. You can improve 100x on Jira just by making it faster, simpler, and easier to use. One suggestion: it looks too similar to Jira, you might want to change the design a bit so that Atlassian doesn't try to sue you or something.
What do you prefer to Jira? At a former workplace we used Gitlab, which was a pleasant suite to use. These days we use Atlassian and often find myself incredibly frustrated by their products
1) Since the definitions are predetermined, drastically removes the room for pedantic circlejerking by problem employees.
2) Bad devs can't pad their stats by making a bunch of bullshit tasks with bullshit time estimates to make them look more productive. Whether a story takes you 10 tasks of 5 minutes each or 1 task at one hour, at the end of the day, a story is a deliverable. The measurable then becomes how many deliverables did you deliver, not how many stupid tickets did you close.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#74Earlier quoted context omitted.
I’ve found jira dysfunction often reflects the dysfunction of the underlying corporate structure.
Yeah, any time someone complains about how many FEATURES JIRA has, it's actually an issue with how their company's management team uses JIRA to micromanage the shit out of them and aggressively optimize metrics that don't matter. But that would be an issue with the organization instead of the tool. And those are much harder to fix.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#75Earlier quoted context omitted.
Fewer features sounds great. I personally loath Jira, and avoid using it whenever possible, but your clone looks really nice. You can improve 100x on Jira just by making it faster, simpler, and easier to use. One suggestion: it looks too similar to Jira, you might want to change the design a bit so that Atlassian doesn't try to sue you or something.
JIRA is great but only in an enterprise where there's a team to manage it, I've moved on from it and I miss the flexibility that it offers - but that flexibility comes with extreme complexity. Most small to medium sized businesses don't need it and can make do with something with less features.
If a job needs to exist purely to maintain a third party tool that you pay for, you probably should find a new tool or make the tool yourself so that the employees work value is retained. It's the equivalent of doing a complete kitchen renovation on an apartment that you rent.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#76I’ve heard that lerna[0] is maybe one tool that can help avoid this type of setup: does anyone have experience with this or recommend any other ways to organize separate dependency configurations within one mono-repo?
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#77It’s slow as hell and even the simplest things in their UX takes multiple clicks. Like resolving a ticket should be as simple as dragging it to done column but JIRA makes brings an additional popup for resolution type. Annoying UX like that.
Definitely a big opportunity to make a dent here.
Feedback: don’t use Atlassian JIRA’s screenshot on the main repo page. Have a screenshot of the UI you’ve actually built.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#78Just a suggestion after skimming the README: the technologies something was built with are not its features. Features are the things the software can do for the end user.
Seriously are you and many commenters here missing the point? Author says several times this is not a product, it's a showcase of his skills as well as a reference codebase for people wanting to learn how to use ts/react/hooks/whatever in medium-size complexity project. The "features" here are technologies used.
> The "features" here are technologies used.
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#79Good to see someone working on this. Jira is awful but they have a strong enterprise hold with a bazillion switches. It’s slow as hell and even the simplest things in their UX takes multiple clicks. Like resolving a ticket should be as simple as dragging it to done column but JIRA makes brings an additional popup for resolution type. Annoying UX like that. Definitely a big opportunity to make a dent here. Feedback: d…
I am recently using a Next & Nest combination, Combining some of the good patterns of this project with Next&Nest combination would be great. Here is a good Next/NEST starter project https://github.com/saltyshiomix/ark
Re: A Simplified Jira Clone Built with React/Babel and Node/TypeScript
#80Earlier quoted context omitted.
Fewer features sounds great. I personally loath Jira, and avoid using it whenever possible, but your clone looks really nice. You can improve 100x on Jira just by making it faster, simpler, and easier to use. One suggestion: it looks too similar to Jira, you might want to change the design a bit so that Atlassian doesn't try to sue you or something.
JIRA is great but only in an enterprise where there's a team to manage it, I've moved on from it and I miss the flexibility that it offers - but that flexibility comes with extreme complexity. Most small to medium sized businesses don't need it and can make do with something with less features.
What we need is Jira and Trello to have a baby