bastijn

Though maybe not the typical case you could start creating spans for user workflows and compare the time it took to do workflow A vs alternative workflow B (in A/B testing). Or you can simply use metrics to collect usage information like how many times a certain action is performed in your system which may tell how popular it is.

I didn't think to much on this but I played with it once in a hackathon and made a tool that showed how one customer site performed versus another customer site by showing performance comparisons on workflow spans and augmenting this information with metrics of most used tools to get an indication if the other site was maybe faster because it used different parts of the product to perform certain actions faster.

OpenMetrics relates to the metrics part of OpenTelemetry, where the latter is currently in alpha/experimental phase. OpenTelemetry has a statement on being interoperable with OpenMetrics for both accepting, forwarding and generating in the OpenMetrics format [0]. So they are two separate CNCF projects where OpenMetrics has overlap with a part of OpenTelemetry.

[0] https://github.com/open-telemetry/opentelemetry-specificatio...

Interesting how none of the top comments have weight in their lists. Number one for me is probably weight as I carry the thing around all day. To meetings, to work/home, etc. This includes weight of the charger.

Next comes battery life.

Next the time it takes to be usable after opening the lid.

Trackpad quality next.

After the other regulars like screen, keyboard, etc.

No, that one was already claimed. https://thousandetherhomepage.com/

I tried to find your pricing models but it seems the entire site doesn't offer them to me. Do I have to create an account ("try for free") to see your pricing?

Unfortunately I have to register to even get a feeling of what this will do.

Also a bit ironic to see curl commands in the first 10 pages I clicked in the documentation whilst the whole product is claiming no code is required.

> All projects that I got into had nasty, unnecessary issues. Almost all of them were started in a rush, to get the business off the ground and had created a parallel business of supporting the customers through all the defects they had. It’s almost like the businesses were caught in a startup limbo, for years. Sometimes decades! Working in such a company can take its toll on someone.

So what is more important to have: (1) a product with bugs which can be sold and raises money, (2) a piece of software that has no bugs but also shipped x-times as late thus only learns you your true requirements x-times as late.

For someone bashing on ivory tower architects in the subsequent lines this sounds like pure irony. The mythical software engineer that doesn't produce bugs.

> Most defects in software come from poor engineering.

In my experience most defects come from not knowing the exact way your software will be used by the customer. Sometimes because of not asking thoroughly but more often because the customer doesn't know yet exactly. Also in my experience most bugs are actually change requests in disguise. Actions that you didn't imagine and never designed your software for but are executed by the customer and now cause trouble to your software.

> Oh and yes, design, architecture and other fancy words, are just engineering in the software industry, because it is not mature enough to have that level of abstraction, in which the architect draws the picture and the engineer implements it in such a way that it almost 100% of the time is right on the money. No. Far from it. What happens in reality is that the engineers try desperately to make the system work somehow, while maintaining the illusion of the story told by the architect.

I feel sorry for your loss. You must have worked in awful environments to think about it this way.

The next few sections I skimmed through read like the author is not proficient in software engineering at all which make me doubt if this is experience from some coding (scripting) side-projects rather than a full-time professional software engineer.

By passing a right to repair on medical devices you also open up the aftermarket for repairs. Would you like to be handed a medical device by your insurance company that has been repaired by an untrained person that considers himself to be a handyman? Or be put in a scanner that was repaired by a service engineer from a broker that is cutting corners to win in the competing market.

Without clear quality and regulatory control there must be an objective method to discern between personal repairs and non-personal ones.

Disclaimer: didn't read the actual right to repair being passed in detail. Not sure if it does discern already.

Maybe. Though one should then also account for the likely case that early adopters were more niche and deeper into the content, being part of an early community. When communities grow it attracts all sorts of people which may decrease the quality of content but because there is more a few gems will still occur. Because they would be hidden behind the "crappy" content they need to be given more points to arise the mass. A prime example is Stack Overflow which almost died due to its own fame (for the early adopters).

Offtopic, Mozilla blog articles like the click through more details one aways have the most awesome images. They almost tell the story without a need to read the text. Other one I remember is the one on webassembly [0]. Similar style images.

They really allow you to scroll through the post quickly and see if it is interesting to read in detail.

[0] https://hacks.mozilla.org/2019/08/webassembly-interface-type...

Seems there are gifs that explain the front page story but on my iPhone I just see static images. It makes it hard to follow the story.

Since it does sound interesting I might visit on laptop tomorrow.

You should offer default images instead of requiring us to upload. That's the power of the spammy meme makers, visit site, type, share.

This is such an open question it is hard to answer. You have to know what runs in the CI as well as size of the project, languages, number of projects, quality steps executed in build, etc. Anyway, to give it a shot:

* multi-million Loc

* number of projects > 50

* languages C#, C, C++, typescript

* Frameworks: .NET Framework, .NET core, .NET standard, Angular, React

* Quality tools in build: TICS, Coverity, Roslyn, custom tools (>10)

* Tests running in build: nunit, msvstestv2, jest, karma

* number of tests running in build > 5000

* package managers used: Nuget, npm

* number of packages (private and public) > 500

Still a lot I forgot now.

It all runs in approximately 45 mins for stage1 builds, stage2-4 run nightly and weekly and take much longer (>2 hours to >24 hours for long duration stage 4). Increasing stages run longer test suites, up to approx 50k or so for stage 3 and 4, more quality checks, etc.

P.s. We spend countless hours reducing our build times. In addition we have setups to split build pipelines for those who do not need the entire archive build for their dev purposes etc. Yet, CI server aways runs single-core and cold builds.

Thanks for reminding me I'm getting old and corporate.

My first two thoughts were:

* Imagine all the smart people in webdev world would improve the existing tool rather than create a new one. [0]

* "if you do less, it will go faster". I.e. Vite is young and new, supports a subset of Webpack and of course boasts how fast it is. Yet my repos can't use it because it doesn't has the support it needs for my repo sizes with legacy stuff. Of course it is "on the roadmap" and by the time it will be supported Vite is as slow (if lucky) as Webpack. Doesn't matter though as a new tool will be there long before Vite reaches Webpack..

Yup. Getting old and also cynical in the evenings. Dammit!

[0] https://xkcd.com/927/

You also have options like https://www.doppler.com/.

There is a lot of "I" in this story. The examples given do not come over as overly genius, but rather trivial. The whole story comes over as written from the perspective the world revolves around the author rather than the author participating in the world. It seems it is the author misunderstanding the complexity of the world rather than the other way around.

Which is probably the larger population as this kind of substition happens most often when a common solution to a common problem is not used.

So, when you notice this happens often and it annoys you, ask better questions. Explain what you want to achieve, what you considered and why you discarded certain solutions whilst you know they are common. If you get a substition beyond all of that chances are the person answering knows what's up. Embrace it, see why it is proposed and simply take time to explain why you couldn't use that (or can). It takes a few minutes but the person answering is spending more than you are, for free. Also you help every next viewer of your question.

I agree, was not in the right mood when I wrote that reply. Should have formulated much more positive.

The points are still valid though so I'll leave it as is. Hoping the authors can still find information in it.

Traffic that comes from Google is not the traffic that builds a community, which they highlight as their strong point. For that you need people who put your site in their routine visits. In addition, right now being small google is not in your favor. It will forward me to SO, not TrueQ. They might want to change their urls as quickly as possible, replacing the question id in the url with the full title to improve indexing.

What I also noticed is that I cannot up vote without having an account. E.g. This question: https://trueq.io/q/18 has a better answer that is not the top answer. I see no way of upvoting it though without an account (did not try to login). Not sure if that is intended. I also see no clear indication of votes on an answer. Even if 0, you should show it. It is the second most valuable piece of information in a Q&A site for me.

Rule number one for a Q&A site should be to not land you on a marketing landing page as main page. Put your questions as main page.

Your layout is having issues atm. It shows less questions in a single screen as compared to SO. It is quite an eyestrain with all the colors (every tag another color, multiple colors in design, icons I do not understand like the eyes etc.) I see comments run out of my screen on ios, iPhone 11 max.

In this space you have one big competitor. Your landing page, which you so prominently slammed in my face, should state why you are worth switching to. Right now you give 3 things that SO already has for ages (and better). In addition to all the things they have and you miss it makes it unlikely I will visit again..

> For the younger readers out there: These are not USB devices and you can't text your friends or watch TikTok videos on them. I know. Crazy.

Makes me remember this open day we organized a year or two back at work. We had some floppy disks laying around and this one kid pulled his dad's jacket and told him that we had 3D printed save icons here.

I have no idea what this is based on what I see in the github repo. The screenshot aren't really helping. If it is note taking with this stack, sounds heavy indeed.

Apart from internet experience (speed, coverage, etc.) this should also be corrected for the purchasing power parity as paying 12USD in Canada is very different from paying that in e.g. India.

On my iPhone 11 Pro Max, iOS 13.5.1, chrome 84.0.4147.71 the "health index of each country" is crashing my tab.

Otherwise, thanks for sharing. Bookmarked just in case.

The screenshot shows a regular board and I need to sign in to see what makes this recursive. Not going to sign in to check out a product (this is repeated over and over on HN).

Could you describe what makes this recursive and/or update your landing page. Not a whole lot to go by now.

First thought after seeing the screenshot was that if this is what is called minimalistic these days the next gen must have come. Fancy ui,

For me it would be worth more if the tool would make sure it would always have line breaks at places which enhance readability instead of only responsive to screen size. The single feature I would want from a tool as carbon is making captures of source code that would aways be super readable, no matter which device my audience reads it. The sample on an iPhone is completely the opposite breaking at my small width making a single line stretch over 4 rows, broken at random points where my screen ended.

It should smartly take my screen size into consideration and find a optimal balance between font size, line breaks and readability. I'm fine doing some small horizontal scrolling if that would improve readability. Kind of a "prettier" for sharing code automatically running when a reader reads it on any device.

User of initial version of the app here. This was my main issue with the app. Lighting conditions influenced the shot color significantly. Curious to learn from the author if the app tries to compensate in any way, and if that has been improved in V2.

I browsed your site and watched the only sample movie you have. For a product claiming automated documentation I guess you are not eating your own dogfood here.

The movie shows no documentation at all except flashing poorly filled API docs which everybody already generates using any doc framework that pulls that from source code comments. The other part of the movie shows options to type documentation and an image that appears when you right click and select UML. The image isn't UML though nor is the movie showing anything on how it was obtained or generated.

I wish you luck but it seems you did not solve the problem yet.

Thanks!

You should put a license in that repo. Witbout a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, it is strongly encouraged to include an open source license.