We’re happy with how this blog has become a resource for developers. We want this to grow, but are also excited with the new releases that are coming. Stay tuned to
www.architexa.com/blog for Architexa releases, events, and other things that the team is doing.
We got the early release of CodeMaps out yesterday. It has been great to hear all the feedback.
Over half the people that came to the site liked it – we are excited to hear that the site is meeting a need. About a third of the people felt like it needed work – we agree, and we are just starting the process (please keep on giving us the feedback). One-tenth of the people did not find the site helpful – we are hoping that as we improve the site and make it’s purpose more obvious that this will change.
For the curious, the above numbers are 53%, 35%, and 11% respectively (we used the the survey forms attached on the site).
The biggest question that we heard about was about the sites purpose. Our goal is big, as we mentioned earlier:
Our goal is to help you use an Open Source Project. We want to help you easily look at the API’s/Javadoc; Make it easy to get a code snippet for using a feature in a library; Simplify finding the right blog post; And even get you a high-level view of the project.
We are planning to start this simply:
First, we want to extend Javadoc – and let you see the source when you need it. Along with that, give you the niceties of your IDE. Being able to easily jump to the caller/callee of a method is often very helpful.
Next, we want to take this fancy code viewer and let you tag it with ‘concepts’. Concepts are the glue that our site uses to connect your code together. And possibly connect your code to things like blog posts, wiki pages, or questions on stack overflow. We want these ‘concepts’ to be used to describe any code concern and can range from a name for some code that you might care about to a high-level architectural principles in the project.
Oh yeah, as we do this, we are hoping that we will have a single site where you want to go to figure out how to use a project. Where for a library that you are using, you can easily find relevant blog posts voted up by the community or just find answers to questions (asked on sites like StackOverflow).
We have been improving the site – please try out CodeMaps, and let us know what you think. Let us know what you think? What should we do differently?
As we mentioned in out last post we have been working on a site to help Java Developers use Open Source Projects. The site is in an early stage but we want to work on the site openly and improve it with your feedback.
Out goal is to help you use an Open Source Project. We want to help you easily look at the API’s/Javadoc; Make it easy to get a code snippet for using a feature in a library; Simplify finding the right blog post; And even get you a high-level view of the project.
Yes, it’s a big goal, but we feel like there is so much that can be done to make out lives as coders easier. We hope this is a good first step in the right direction.
Check out the site: http://CodeMaps.org. If you can’t find your favorite project we can help! Click the ‘Add Project’ button on the top, and our engine will import the project for you to view.
Oh yeah, make sure to let us know what you think. We want CodeMaps to grow into something that you use want to tell your friends about!
Whoops! We made a mistake.
We have been trying to build something amazing to help developers quickly understand how to get moving with large projects. As we have been doing that, we have been hearing a growing set of requests for help with Open Source Projects.
We have spent the last last few months improving our engine and building a couple of cool features to help the users with open source projects – in large part based on ideas that were sent to us. Well, it’s Spring, and it’s time to pull the covers off.
We are almost ready for our public release, but before that we want feedback from the community on what we have built. Want to be one of the first to find, sign up up now here: http://atxa.io/Hsv3Mx
Update: Some of our initial visitors had some issues while completing the feedback form. We apologize for it and the issue has been fixed. If you face any issues please drop us a note at firstname.lastname@example.org. Thanks!
Eclipse is turning 10 years – and we have been in a mood to celebrate it. We have been involved in a lot of Eclipse related events in the past, but wanted to do something special this year.
If you are in Boston, come join us next week. We will be having free pizza, beer and even a birthday cake. We will have a bunch of people who really know Eclipse inside-out and will be showcasing a bunch of the cool technology being built these days.
Time and Location: We have planned to have the event on 17 November 2011 at 6:30PM, at Constant Contact, (Reservoir Place, 1601 Trapelo Road, Waltham, MA 02451 – see on map).
More details on the Architexa Company Updates.
Today Architexa’s “Working With Large Codebases” blog has posted it’s 50th post. While not a huge number, we are excited to see the response to so many of our articles for helping developers work with Eclipse, with agile teams, use design patterns, and document and communicate ideas with developer tools and diagrams.
Architexa has been working on the performance of our diagramming tools, and conducting user studies to find more about what it takes for a developer to understand code. We have also been improving our Open Source documentation site codemaps.org.
With all the articles out there helping developers understand code, we were wondering what type of information you would like to see more of?
We are looking forward to providing much more interesting content in the coming months. Please let us know what you would like to see. Send us your favorite articles from our site or across the web.
We are working hard to help developers easily understand and document code. One thing that we have noticed is that the open source community continually faces challenges in these areas. New developers join projects frequently and at times committers have to leave a project. Without quality documentation code can quickly deteriorate.
We are great supporters of Open Source Software and have wanted to contribute by making it easier for developers and the community to document their code. As of today, we are providing free licenses for the Architexa Suite to those willing to upload good documentation, add comments, and vote on good diagrams every week. We will also appreciate it if you can give us feedback on what would make the Architexa Suite more useful for you.
The great part about being a coder is that we like building software that will make a difference. And not just that, we like taking on hard development challenges to build out simple solutions. Bringing these solutions to those that can benefit from them is another challenge in itself; one that many developers often have not had any experience with. Sure you can throw your code up on source-forge and hope people find it but if you really want to change the world you often have to put in a little more.
One of the nice things about launching a tool is the opportunity it allows in talking to our users. Over the last 3+ months we have spent a great deal of time talking to development teams about Architexa, and have gotten a great deal of insight not only into what they like and don’t like about Architexa, but more importantly, what pains they have felt. The consensus is clear: while developers do need to focus on coding on a day-to-day basis, to be successful on a long term they need to worry about the parts of the system that are shared between team members. These worries where what we focused on for the most recent release (v2) or Architexa.
We have had a wild ride the last two months – which is why I have unfortunately not been able make many posts recently. Since we launched in June, the response for Architexa has been great, and after getting invited to apply for MassChallenge we entered into one of the largest startup competitions ever with around 500 entrants. Three months and a lot of mentoring later, we emerged as runner-ups. Yes, being selected as one of the top startups at MassChallenge is great, but wow, did we learn a lot!
Read more on the Architexa Company Updates.
We have been working hard so that programmers can easily work with large codebases – whether it is in making sense of the code that you have, documenting it, or just discussing it with team mates. You will notice that we have built a set of powerful but easy to use diagramming tools. We believe these tools will help you and your team work more effectively.
Read more on the Architexa Company Updates.
We have been extremely frustrated with UML tooling in the past, and for the last 2+ years we have been building something very cool. See the video below:
Can’t see the video? Click here
Most UML Tools focus on creating diagrams before coding, but we believe in having diagrams made from code. Where other tools require months of work to get something useful, we want to get you useful results in minutes if not seconds. Some tools require reading lots of documentation to use, but we have wanted a tool that you can get up to speed in 5 minutes.
What do you think of it?
(interested? sign up and use on our homepage)
Over the last two weeks, we here at Architexa have been overwhelmed by the positive response to our vision (see video on our
… always liking to use UML to understand and navigate source code that is not mine and that I have to change. Or even my old code that I can not remember exactly how it is organized. However, I have never been able to create a lot of UML diagrams and use them to generate the skeleton code. So my pattern of use of these tools fits well with the philosophy of Architexa.
He went on to say that
The difference with all the [Architexa] tools is that they are designed to “surf” the source code through UML diagrams, so that one may be viewing more or less detail as you need. It is not an all or nothing, which is usually the case with\ traditional UML tools.
A poll trying to find if developers let their UML/design diagrams go stale, recognized that “sometimes it can be too much work to go back and update diagrams once the coding process is underway, especially when under a tight deadline”. It found that over 2/3rd developers noticed that with today’s tools their diagrams go stale with them falling back to their code.
One of the editors at JavaLobby, James Sugrue, did an an interview and talked about how Architexa makes life easy for developers. He talks about seeing a huge potential in our tool “for helping out with code reviews, or for getting into a new code base”.
In the Social Media world, it was nice to be referred to as the next generation of UML tools:
Since exiting the beta, we have been encouraged by the response and are letting people in to use the suite as fast as we can. We want to make sure developers have a great experience with our suite and we want to provide a great level of support while doing that.
We will be releasing additional videos and information on the product soon in addition to the (hopefully) informative content you’ve come to expect.
Here at Architexa, we have been hard at work on an exciting new vision – one that we believe will make our lives as software developers much easier. As our software has grown into a powerful suite of developer tools, we have been wanting to share our ideas with you, and also hear what you think about what we’re doing. We decided to launch this blog so we can better communicate with YOU: the software developers who inspire our work! Check in frequently to see what we’re up to. Your feedback is really important for what we do, so tell us what you think: what you like, what you don’t like, and where you think we should be headed. Also let us know if you have any tips that other developers might benefit from – we will put them up.
Welcome to Architexa blog! We look forward to connecting with you!