Time, heavy task, and a look ignorant force, this is my first experience entered into this group. The company is still very open-minded, ever since I applied to do the front soon assigned to the project. Use Xamarin.Forms development project, it simply is similar to that of a cross-platform framework for WPF stuff. (Of course, I was not very familiar with WPF, smile). Boss mean removal of some other reason outside, Xamarin is also based on C #, so I better get started may be relatively few. I did not expect this to get started to open the "endless" mode overtime.
Business process is not long, only a few pages, corresponding to some basic CRUD functions, in addition to the front and I have developed with another proficient WPF chiefs, so I am still very confident to complete the task. However, always the ideal and the reality is not a small gap. Gangster In addition to this project also involved in maintaining a number of other projects, so the project can not be placed on this day. And for some reason, in the middle chiefs also took a week off. Knowing the news, my heart is collapse. After all, before the contents of the tip can be said to know nothing, I can only bite the bullet on.
I recall at university military training, instructors, and we talk about "a force to force their own, or do not know how much of their potential." No way, what school do not understand it, do something to take the time to slow strike . Eventually, the four classes six days a weekend in Riga, regarded this project bite down. My people have an innate worship of technology heavyweights. There is one that one, the big brother of the technical aspects of the same group is cattle, the code is very elegant, looks very comfortable. Although just graduated when compared to my own code has also been a lot of progress, but still well short of this level. But beyond technical aspects, compared to the previous leadership, in fact, I was a bit disappointed. We should all understand the life cycle of a project of COSCO more than "writing code" This part, at least also includes requirements analysis, scheduling, task allocation, function realization, many aspects of code review, testing and so on. But the chiefs seem to care only about their own to achieve this part of the function is responsible. Does not mean that I do not want to take on more responsibility, but I work until ten o'clock, you are off work at five thirty. My weekend two days weekend your weekend is a bit too much? Later, the project manager also talked to me in some cases the chiefs, to pick what children to and from school, I can only say that I try to understand it. Just this comparison, how much my heart a bit uncomfortable.
Bowen have said before, good technology leadership experience will help you a lot, do not fly another encounter, no matter what technology leadership in fact, too, because you want to pit one by one stepped on. Although completed on time, but I want to make my own evaluation of the quality of the code, I can only say wonderful combination of a garbage can run the group together. (Mainly refers to the part that I wrote, smile). Although the less important aspects of code review, but the code written or rotten roots of me. Time is too tight, the development process Gangster regular leave, and more emphasis on my side of the task. I am here before the front-end content are not very understanding, only one side to find information, while doing the function, while repair bug, while adjusting style, wait for multitasking.
But it is also because of this, the entire front end of the project in various aspects involved have learned. Although Xamarin very small minority, but I think compared to other front-end development language, the essence is the same. A mobile application, can not escape what page style, user interaction, data storage, data exchange with the background, error handling, and other aspects, and when you should do something with something, I also have some understanding of how much. Sometimes combined with some back-end development experience to do before, angle of approach really has changed. And when the rear end of a small partner integration and can understand some of the difficulties of their development process. And one thing to feel ashamed, do the back end of the design before the interface, model definitions often without deep thought, leads to the front of my colleagues. "Rework." Still writing API days, that is not more than a few fields, put a list into an object in the Well, no big deal. But now I realize that maybe you just think you change the type of a column, or a little structure changed a bit, but the impact on the front end could be enormous. Another profound experience in terms of the robustness of the code. When doing the back-end development, is not an exception to catch, nothing more than an interface in return values, or of some 500 serious mistake, of course, more serious, but still failed to attract much attention. App is not the case here, is also an exception, you may cause the entire application to crash out, if it is some complicated series of operations, you might set aside all the previous operation. And for customers, applications often flash back is extremely annoying. Which led to flash back it may be just a small mistake.
Some people are working for ten years with one year of experience, and some people a decade of work experience. I think the difference is that reflection and summary. The code sucks, the development process is also very hard, what's the problem then?
- I'm using Visual Studio for Mac, Gangster use Visual Studio to develop and remote on another Mac. Though we have used such a tool Xaml Style, but there are still some format problems. These format led me sometimes the entire file conflicts in the merge codes, merge time-consuming.
- I am very interested in git command line, and do not like it "cool" and "programmer that looks like." Although the entire project, because I do not use git while some mistake, but compared it SourceTree, fork these tools, more efficiency is really low. Especially when conflicts arise. My question, should be rational use of tools.
- Visual Studio's powerful As we all know, it is with these thoughts, embarked on Visual Studio for Mac pirate ship. The result is non-stop Caton, once the collapse of several hours, listening somehow not break, from time to time does not respond, really helpless. Visual Studio for Mac can expect more and more Okay, but I'll get up early project should no longer apply for a Windows machine to the remote to your Mac.
- Code side, the page layout using a lot of hard code, resulting in a lot sometimes a small change in design, I need to adjust place. In fact, the question I have been looking for a solution, but behind closed doors, did not think of a better solution. Root of the problem is that, just look at the design draft, I can determine some of the more common style and color as a resource. Then these same place to use this resource. For example, Title and probably the top left of the page navigation buttons, and the following Button is the same color, but after some time if the designer and the customer's confirmation just updated the Button color, how can I do it? Just set up a separate color Button Mody, then and now HardCode What is the difference? In addition, I may observe some of the common Margin property, but each page may have some subtle differences. This time how should I do it? It is to ignore these differences using a common unified Margin (does not comply with the design draft), or Margin set individually for each small change (and Hard code What is the difference)? If anyone garden friends can figure it out, but also hope the wing.
- Handle some business, too close to the underlying implementation, not abstract, source utilities degree is too low. For example, to display or hide a button according to a Boolean value early in the project I went to write a conversion logic Boolean values in each place will, behind only aware of this stuff Converter. The reason is that on the one hand, the front end of the language used is not familiar, on the other hand too much care about progress, ignore the link "thinking". In other words, just want firewood, did not think about how good sharpening.
- Not thinking or looking for some "best practices", just a lot of time to do a feature on their own YY, I thought about, and then hands to do it. For example, a Popup, just pop up is no problem in the simulator can be better run. A real machine to run only to find the real machine on the input box will pop up a virtual keyboard, and this affected my keyboard layout, resulting in the Popup a mess. The main reason for me, not enough time is no time to study one aspect, in addition to the normal project code review should also reduce the part of the case.
- Problems mentality, the back-end experience two years ago, the base will not encounter any technical problems, if any, you want to know about which aspects to look for. This time there are times when I spent a lot of time to solve the problem, in fact, as long as it's easy to solve. Should I set myself a time, research on an issue more than this time actively seeking help, maybe someone else would have encountered this situation, do not you think perhaps the key question, so you spend again much time google could not find the answer you want.
Although bitter force, is Xamarin.Forms + Visual Studio for Mac tortured want students ecstatic, but so to sum up the harvest, or find many. Compared down, I might still prefer to develop some back-end, there is a direction, and good work.