Connect - will it ever get fixed?

Reggie,

No, I've run out of time...and obviously patience. How about we start by dealing with the 20 or so open defects I've already filed since product release (not to mention the ones in beta that still aren't fixed). It seems pretty pointless to keep spending all my time logging issues that may or may not get fixed at some unknown point in time.

I don't believe anybody could complete a real project with this product. At least not if they are trying to incorporate any new "features" like parmemetrics or items. I've try, given it my all and now I'm screwed because I can't deliver files that are stable and have no idea when or if they will be.

I don't want to take this out on support people because they've been dealt the same crappy hand as the customers. This was clearly a management decision to shove this out the door prematurely. Now you guys are on the front line trying to defend a really bad position because somebody in the rear pushed thru a bad plan and I'm telling my client "Sorry your building doesn't really need doors does it? Well maybe you can have them when someone at BSI gets their act together." Maybe they were right and I should have used AutoCAD like they wanted me to.

Hi MJAN,

Unknown said:

uuuuhhh by August 2001, Microsoft released Windows XP being first x64 OS > you may do the math.

Frankly, how the release date of Windows XP is related how long Bentley developed 64bit MicroStation? Do you really think Bentley (and any other company) started migration to 64bit platform when Windows XP 64bit, one from the worst piece of the software released by MicroStation, become available? Until Windows 7 there were not even too many users of 64bit Windows at all.

Taking into account all technical conditions, which I can evaluate better then business ones, like stability of platform and API including drivers, availability of good compiler (both C++ and C#) with features required to link together all used modules and technologies (like Parasolid core, DirectX subsystem etc.), I guess it took few years, but not 14 for sure.

And many companies, even the big one with plenty of users, still have not released 64bit versions of their products (like ESRI with ArcGIS for Desktop). I guess simply because it's pretty costly and complicated path.

Regards,

  Jan

Unknown said:

In house testing can only go so far.

I don't deny that there are some complex issues that are bound to arise only in real world... but...  the default browser for Windows 10 is EDGE which Help doesn't work on.  (Defect 7000402018) and was reported during the EAP.   Seriously how hard can it be to see if Help works on a default install of a "certified" platform?

There were plenty of other known issues as well and the defects I've uncovered have surfaced doing first attempts at some very simple tasks.

Bentley has a lot of resources at their disposal.  This product is simply showing where their priorities are.

Unknown said:

Bentley has a lot of resources at their disposal.  This product is simply showing where their priorities are.

It's pretty clever note! In fact there are never enough resources (developers, testers, documentation writers etc.) in software development ;-), but there is always a chance to change resource allocation and I agree the results express company priorities. From this perspective I am not sure if MicroStation is really top priority, me feeling is more the priority is to develop or acquire many products but afterwards there is no capacity to keep steady active development matching competitors.

Regards,

  Jan

Unknown said:

Bentley has a lot of resources at their disposal.  This product is simply showing where their priorities are.

It's pretty clever note! In fact there are never enough resources (developers, testers, documentation writers etc.) in software development ;-), but there is always a chance to change resource allocation and I agree the results express company priorities. From this perspective I am not sure if MicroStation is really top priority, me feeling is more the priority is to develop or acquire many products but afterwards there is no capacity to keep steady active development matching competitors.

Regards,

  Jan

Wellcome to age of (fr)agile development... I blame it all on Facebook and their ilk :-)

Unknown said:

Wellcome to age of (fr)agile development

We have disgreesed a bit from the original topic ;-)

To associate fragile (and bugs etc) with agile development is a huge incomprehension what agile is about. It's just a concept, it's even not a methodology, and if used wrongly as any other software development style, it leads to buggy software necessarily. But it's not because of agile, but because of wrong development. Agile itself is in fact more resitant and better suited for bugs hunting and it doesn't tell anything like "bugs are allowed", but unfortunately today "agile development" is often used as an explanation / excuse why software is not good :-(

Edited: The linked video is nice :-)

Regards,

  Jan

I loved the  video I couldnt  stop watching it  had to go to the  end!  very interesting and explains whats going on in the world  not just software but products!

yea... we the users or the Product Owner are dragged into 'writing the spec' or defining the product as the product is developed. It's all about muddling through in search of the 'Right It'... but the problem is that there is never enough time to build it right after (Technical Debt) before some other crisis like Windows 12, port to 128bit etc etc comes along.

I think UI quality is the first to suffer when balancing the need to clear Product Backlog and technical debt and still meet sprint deadlines. I suspect after a few years of this way of working the devs become one-trick wonders with shrunken hippocampi due to PTSD. They then fire the PO who couldn't formulate the product vision or requirements (the Right-It) anyway because they haven't been in a production environment for years... go home.. drink some beer.. repeat.