HereBeBeasties (u/HereBeBeasties)

HereBeBeasties commented on Ask HN: What's the best tool you've used for sprint planning in 2025? · Posted by u/jackh04878

HereBeBeasties · 3 months ago

fibery.io - it is excellent. You need to configure it, although it has various templates to get you going out of the box, including sprint-based development.

The nice thing about it is that you can add whatever you like, however you like. Want components with default owners for tasks? Want milestones? Want stakeholders? Want sign-off reviewers? Want to integrate with existing tools like Linear or Notion or JIRA or even email inboxes or Slack messages? Add entities for Incidents, that automatically make a dedicated Slack channel when you create them?

Want proper 1:1 or 1:manu or many:many links between Tasks and Milestones and Sprints and Incidents and Teams and Components and whatever?

Want single assignees? Or multiple ones?

Want flexible custom reports on all of it?

Or just want a simple flat Todo list, that can evolve later to fit your needs?

Stop having the tools dictate to you how you work and instead set it up how your company actually wants to work. That's Fibery.

(I am not connected to the company, just a very happy user.)

HereBeBeasties commented on Setuptools version 78.0.1 breaks install of many packages github.com/pypa/setuptool... · Posted by u/computronus

jarboot · 5 months ago

The current approach of the maintainers terrifies me -- de facto standards should be respected. Even if something is invalid like `description-file`, if it is present in 12k repos it should raise a warning and not break anything.

In the rationale for this that I can find [1], a maintainer says the following:

> I'm inclined to say we should do it, even though it will cause some disruption.

They also say an alternative is to "accept the status quo", which is exactily what they should be doing. I can't find maintainers giving a compelling reason not to support this status quo of `long-description` as an alias to `long_description` besides "simplifying code." Code simplification should never take precedence over massive breakage of compatibility.

[1] https://github.com/pypa/setuptools/pull/4870#pullrequestrevi...

HereBeBeasties · 5 months ago

It seems that the person who did this acted unilaterally, with no code review, and ignored (then disabled) broken tests while landing this (https://github.com/pypa/setuptools/pull/4909). One should not be too harsh - he seems to be a student. One perhaps should be more harsh on the commerical entity sponsoring the project, though - setuptools is sponsored by Sonar via "Tidelift". According to https://tidelift.com/subscription/pkg/pypi-setuptools:

> The maintainers of setuptools get paid by Tidelift to

> implement industry-leading secure software development

> practices and document the practices they follow.

Well, that really doesn't seem so in this case now, does it?

HereBeBeasties commented on Atlassian announces end of support for Opsgenie atlassian.com/blog/announ... · Posted by u/anurag

hinkley · 6 months ago

Atlassian is nothing if not consistently mediocre at integrating their purchased properties into each other.

And they still haven’t finished making deployments have feature parity with builds in Bamboo.

I made it partway through the interview process at a startup a couple weeks ago and realized I didn’t have a good answer if they asked my advice for what to use for project management, if not Atlassian. Which was fairly likely given the company maturity and the position. I’m still trying to find that answer.

Aside from GitHub I only have one other answer and it starts with, “this is going to sound crazy but hear me out.”

HereBeBeasties · 6 months ago

Fibery is the answer. It's absolutely great: https://fibery.io/

HereBeBeasties commented on James Gleick's Chaos: The Software github.com/rudyrucker/cha... · Posted by u/signa11

HereBeBeasties · 9 months ago

Honestly, all you lot complaining about the speed of 286s or 386s!

I have fond memories of implementing a Mandelbrot set renderer on a CASIO fx-7000G graphics calculator. 422 bytes of programmable memory! The TI-93 I did it on later was considerably faster and easier to make it fit in. :-)

HereBeBeasties commented on Realizing the dream of good workplace software campsite.com/blog/realizi... · Posted by u/monkey_slap

HereBeBeasties · 10 months ago

fibery.io all day long :-)

It now has a thread view so you can replace tools like Slack with it, and entity-grouped notifications, so you can easily catch up on things if you are away for a few days. Plus it does a much better job of proper knowledge management, with references, proper relations, build a domain model of your business, per-entity and linked-entity permission models if you need that, etc. etc.

It provides integrations for existing tools, so migrating to it is much less big bang (sync in your JIRA tickets, Linear, Slack conversations, etc.).

Two-panel nested views on entities make navigating through status on task boards, projects, etc. a joy. You can build automations (create a new Slack channel and invite the assignees to it when I make an Incident, add a 'priority' labels when certain people comment or certain keywords are used", etc.).

Add meeting minutes, automatically convert the follow-up bullet points in those into Tasks for people and assign them, without ever leaving the same single page view.

You can use it a bit like e-mail, and a bit like JIRA, and a bit like Slack. And you can pick and choose those "bit like"s to best fit your needs.

We haven't completely replaced Slack with Fibery, but we've moved most of our more intentional communication into it. We no longer feel we need to "complete Slack" to catch up on the state of the world.

We love Fibery and are very happy customers. ♥ It's great.

HereBeBeasties commented on Ask HN: Should we bring software dev in-house? · Posted by u/45HCPW

davedx · a year ago

$5M/year? In the US maybe.

A team of 5 senior freelancers in Europe will cost about 150-200k per person.

HereBeBeasties · a year ago

Employer tax contributions

Office space

Hardware and software, SaaS licensing, cloud costs, etc.

Hiring costs (recruitment, recruiters, time lost in selection and hiring)

Secondary cost to rest of the business to change processes, retrain, integrate, help the dev team understand requirements, effectively build and iterate, etc.

Quite possibly a bunch of compliance, security, audit, pen testing, and other regulatory costs depending on the demands their clients have, etc.

Running a team != hiring a bunch of freelancers as a one-off.

HereBeBeasties commented on PKfail: Untrusted Platform Keys Undermine Secure Boot on UEFI Ecosystem binarly.io/blog/pkfail-un... · Posted by u/jeroenhd

HereBeBeasties · a year ago

List of actual affected devices - https://github.com/binarly-io/SupplyChainAttacks/blob/main/P...

HereBeBeasties commented on CrowdStrike Update: Windows Bluescreen and Boot Loops old.reddit.com/r/crowdstr... · Posted by u/BLKNSLVR

mr_mitm · a year ago

They say it was caused by a faulty channel file. I don't know what a channel file is, and they claim to not rely on virus signatures, but typically anti virus product need the latest signatures all the time and poll them probably once an hour or so. So I'm not surprised that an anti virus product wants to stay hyper updated and updates are rolled out immediately to everyone globally.

HereBeBeasties · a year ago

No, I'm not surprised either. But if you're operating at this kind of scale and with this level of immediate roll-out, what I would expect are:

* A staggered process for the roll-out, so that machines that are updated check-in with some metrics that say "this new version is OK" (aka "canary deployment") and that the update is paused/rolled back if not.

* Basic smoke testing of the files before they're pushed to any customers

* Validation that the file is OK before accepting an update (via a checksum or whatever, matched against the "this update works" automated test checksums)

* Fuzz tests that broken files don't brick the machine

Literally any of the above would have saved millions and millions of dollars today.

HereBeBeasties commented on D3 in Depth d3indepth.com/... · Posted by u/lobo_tuerto

amelius · a year ago

Can anyone recommend a good plotting library for Python, that is not matplotlib?

HereBeBeasties · a year ago

https://opensource.com/article/20/4/plot-data-python gives some common options. What kind of plots are you trying to achieve? Interactive? Jupyter notebooks? Reporting? SVG or HTML output? You might also like to look at things like https://evidence.dev

HereBeBeasties commented on Spotify will reduce total headcount by approximately 17% newsroom.spotify.com/2023... · Posted by u/filleokus

atbpaca · 2 years ago

I wish CEOs would resign when layoffs happen. It should be like some governments where the whole cabinet resigns. If layoffs are a necessity, then the CEO and the top management should show the example and take responsibility for taking the company into the wrong direction, leading to layoffs. That would be fair and more understable than a "thank you for your hard work and commitment".

HereBeBeasties · 2 years ago

Lay-offs aren't necessarily a sign of failure or bad strategy, so your logic does not compute.

Lay-offs happen for all sorts of reasons. It may be very reasonable to have X number of people one year, but changed market conditions, or financing rates, or whatever else mean it no longer does the next year.

People don't have magic crystal balls. But even if they did, it may still make sense to hire people while financing such a thing is cheap, and to lay those same people off when it isn't any more. Make hay while the sun shines, and all that.

You may not like the fact, but getting rid of poor performers makes businesses stronger and better. Rounds of lay-offs undeniably make such decisions easier to make and justify in large companies.

CEOs who do the same (or more) with fewer resources are generally rewarded. As a shareholder in the company you'd want them to do more with less and make you more value, right?

You might as well argue that any CEO who needs to hire more people has failed. That sounds obviously silly, but it's genuinely an almost equivalent argument.

All of this may not be pleasant for those involved and especially those who are losing their jobs, but that's capitalism for you. Big business doesn't tend to optimise for people's feelings - it cares more about the bottom line and being competitive.

In this case there is an obvious and pressing need. The streaming music scene may be a tremendously complex place to operate a business in, with all it's licensing and labels and countless jurisdictions and legal complexities, but both Apple and Google are sitting there ready to eat Spotify's lunch if they can't figure out profitability.