Hacker Newsnew | past | comments | ask | show | jobs | submit | qxmat's commentslogin

A fellow super brain finalist on hn?


Was that the name of the contest? I don't remember now! There are some pages about it in archive.org but very hard to find.


Jira's now discontinued server version had a sequence table to stop you sharding it. It also made disaster recovery from a hard shutdown awful. I have nothing good to say about Atlassian.


Atlassian, and JIRA specifically, are responsible for so much wasted time and capital expenditure. If I could get ahold of metrics like "hours spent building, using, and maintaining JIRA" versus "value obtained from JIRA" for each of the companies I've worked at, I'm pretty sure I could generate a report so scathing that nobody would ever use it again.

Gatekeeping your work organization system from the people working on, and often MANAGING it is such a huge friction point I'm amazed they ever got clientele. I'm an Admin on a project right now and I can't change our status types without going through our assigned Atlassian rep.

And don't even get me started on the dumpster fire that is BitBucket. Ever tried to use the API? it's somehow even more worthless than the UI.


Their Windows sensor has made development almost unworkable. Not sure why but I haven't noticed the OSX sensor slow things down appreciably. I suspect my Windows profile is configured to be more aggressive?


Knight Capital!


https://www.bugsnag.com/blog/bug-day-460m-loss/

It made me laugh! And cry inside


6 days is pretty reasonable to me because I'm an avid supporter of the release train (miss the release train, wait for the next one).

Governance is an important aspect of the software development cycle past the PoC stage. Releases shouldn't lead to an existential crisis.


This is something I've been unable to articulate as succinctly as you have - thanks.

In the past I put it down my experienced approach and what I need from others: make it work (mediocre solutions that deliver 80% value are fine!), then make it better (reflect and refactor until readable/approachable/idiomatic) before finally (stretch goal) make it faster (break idiomatic paradigms, vectorize etc.)


Python has a few weird issues like this. The last one I encountered was with a class inheriting Thread, join and the SQL Server ODBC driver on Linux. Fairly sure I hit page faults thanks to a shallow copy on driver allocated string data but didn't have the time to investigate like the hero of this blog post.


This appears to be the domain of Dagster + dbt, with which you get data lineage, not just composition.


Modern frameworks rely on components and the shadow DOM. If you understand how these are implemented you'll go far.

One of the trickier things to grasp is where your CSS begins and ends. CSS is quite leaky here but there are ample style guides that illustrate pitfalls.


I also found the C#/F# courses very well made. Specifically those by Mark Seemann, Kate Gregory and K Scott Allen... who I just found out died 2 years ago :(


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: