At least for me, the killer feature of PostgreSQL is its procedure language PL/pgSQL. By a fortunate accident, I had the opportunity to write some complicated features (read "calculation heavy") for a web app using PL/pgSQL. Once coupled with triggers, you can just leave everything to the DB to the point, controller has to do nothing except query and return JSON objects to the front. It is so expressive, powerful, efficient and reliable.
I have worked with MySQL, Oracle, MSSQL and as of late MongoDB. Given a choice, I will always settle for PostgreSQL... it is just so natural to work with.
I was a dev in a firm that pledged to do things agile/scrum way. However, nobody knew how to do it in the "text book" sense. As you can imagine, it went horribly wrong, especially for large web projects. Same firm, then tried waterfall, similar disaster.
So I conclude, workflow doesn't really matter. If the team you are working is not properly functioning as a team, likely no workflow can help you.
What I call a properly functioning team is a team with members who has a common goal, willing to sacrifice and work hard to achieve it, and willing to help other team members. Unfortunately, most organizations are driven by appraisal systems, which by design down play team work.
I support the motion of *not* calling programmers as engineers.
Starting from the academic point of view, engineering curriculum is far more different than a CS. General undergraduate engineering course comes with number of core modules with the purpose of teaching basic "Engineering Concepts". Furthermore, engineering courses are focused towards "skills training" by range of hands-on laboratory classes, design projects, team projects etc, to learn skills such as see the big picture, learn how to operate instruments, safety, planning etc.; which are a must to function as a professional engineer in industry. Then once in the trade, engineers generally become a member of a professional body e.g. IEEE, IEE, etc. and they are sworn to obey their code of conducts.
Switching gears to my personal story, I trained as an electrical & computer engineer. After a stint in telecommunications industry, I went on to work in web development. I was quite appalled by the way "programmers" think and execute projects in general.
When I worked in the telecoms, I observed that engineers spend quite a long phase in planning before actual execution. In the process, they have to comply range of regulations on telecoms, environment, etc.; and not to forget other concerns such as the commercial interests, backup plans, future expansions, long terms sustainability, maintainability etc. Overall, they consider the "big picture" and do not bog down with just the technical aspect. When it comes to execution, it is generally smooth and trouble free (usually there is a research & trial period before actual execution). Overall, I've seen much more customer orientation and long term view in engineering firms.
When I worked for the software house, planning was considered a "waste of time" (and not to mention, practises like Agile are generally up the anti). And most often or not, you build the roof of the house before the foundation, then figure out how to connect two of them. By and large, there was poor customer orientation. And most damaging of all, lack of concern or thought on long term view of the project and its outcome. I've lived through many cycles of delivering half-baked solutions to client and milking them on the long run to fix those solutions (and in the worst case scenario, making client go bust). If it is a proper engineering firm, they will be sued for such kind of misconduct for sure.
I worked for software industry in far east -- a small city-state popularly known as 'the little red dot'.
The firm I have served there had the terrible conflict of interest, where development team delivers rotten products to clients, which will be fixed to a barely operational state later by the maintenance team for a hefty price tag.
Developers always had to ship code, regardless how many bugs or security loop-holes in the product. As you could imagine, project timelines are always half of what it should need. Managers are micro-managing to the point, developers have to report progress every 4 hours. As long as half-baked features are there in a barely demonstrable state, project/product is declared complete by the manager, and the senior manager is happy. Otherwise, developers are forced to admit that they were lazy and incompetent.
Still, none of our clients was happy. Some clients even went bust. The only reason why we had a clientele was, they invested too much that they can't do a U-turn. It was frustrating! Despite being registered as an IT service company, we gave middle finger to the clients far too generously and openly.
I have complained through official and unofficial channels (i.e. in meetings with senior managers behind closed doors) about this unethical practices. Reply was, "This is how we work, we don't care about our clients. If you don't like how we work, the door is open for you to leave".
2 months ago, I was fired. Though they have given ã different reason for the dismissal, their hidden message is "You never played by our rules. Just go away".
As long as corporations operate by the mantra "money over all else", nothing would change. Its a dystopian future after all.
I came to software industry quite late at the age of 27. I worked for number of web development project in Java. And I was fired a month ago saying I am "not a good fit for the team".
The team in question is full of fresh grads (and I was the only non-chinese person), who are willing to work 18 hours a day, 6 days a week; tech leads and managers are around my age, and still they can't do a simple project without a major re-write 2 weeks before going live. Since I don't speak fluent Java, I was often look down for being a "non-technical" person. Still, every project I had control, I made sure work flow is optimised, everybody is in same page, requirements were correctly gathered and most important of all, managing client expectations and keep them satisfied.
For the past few weeks, I tried looking for a similar job. Most companies are unwilling to hire someone in 30s. And as someone mentioned above, most Java jobs asks deep technical questions (and trust me, you will never use those concepts in real world). And also, lot of companies do not want to pay my previous salary level even.
Then I tried Business Analyst positions, and most companies turned me down saying "you have no experience in this domain" or "you haven't done UML before" etc etc. Same goes with project management or other possible jobs in tech line.
To be honest, at this point in my 30s, I feel like I am quite redundant in software industry, and my skills are worthless. It is quite hard to change careers, as I do not have experience in other domains like finance, healthcare or education. Looks like future is doomed at this point of time. I just can't emphasize enough to anyone who is willing to land in a tech career.
For a start, telcos these days have very stringent bandwidth caps. For an example, here in Singapore, a 2 year mobile data plan with 12GB/month costs ~USD 200/month. Other than light usage (e.g. browsing, bit of skype and youtube), you can't do much.
And what about power consumption ? how fast can it drain your phone battery ?
I completed my PhD in EE/CS 4 years ago. Right after submission, I was unemployed for 6 months and during which time, I applied for 1000+ positions. Only on my 3rd interview, I was offered a junior dev position with minimum compensation in a SME.
Initially, things were good. I paid my bills and was doing many things I couldn't do as as a grad student i.e. going on holiday, fine dining, drinking binges. Work wise, I enjoyed the first year or so learning and coding new languages/platforms.
After a while, I woke up to the fact that my firm has deep problems in terms of work flow and project management. Almost 90% of the web projects we completed in last 3 years were failures. Perhaps I was too naive, I fed them back to the management and highlighted that the problem is with our SDLC and some incompetencies in mid-layer management and tech people. This did not rhyme well, I was kicked out from dev team and transferred to a different department; and my promotion was denied while every other fresh grad was promoted before me.
Overall my experience is, PhD can work against you. For a start, bosses are always intimidated with your superior intellectual brain and over the top communication skills (and don't forget, most bosses will be at your age too). Other aspect is, rest of your co-workers been there or has cut-teeth in corporate politics, so in an event of political power-struggle, quite literally you don't know what to do. Also most firms has no idea what to do with a PhD qualified human resource, let alone having a boss who can manage one. Lastly, not being mastered in some technologies (like Java) can be a disadvantage.
As of today, I'm feeling quite dejected and unappreciated at my firm. Lately I am looking for a new job (preferably something outside IT). I don't know what the future holds for me. As much as I regret taking up above position, on the hindsight, I landed on that position during recession years and helped me to sail through those critical years.
Short answer: I made a similar horrible mistake... and only now I'm regretting.
Long answer: After my graduate studies, I joined to a SME, which was supposed to be in between start up and IPO (this is in far east in Asia). Though the company rolls financially, human resources are what I called "Sub-par" quality. Simply because they don't have any real competition, they think they are the best and ignores all other good ideas coming both internally or externally. In addition, there are no standard workflows to handle situations. So working in such environments is analogous to running around with your head on fire. Lately we have done few projects that are, by all means, text-book quality death marches. Finally, as everyone is pretty young (& not to forget, dumb!), it is pretty hard to get them on the same team spirit and work ethic... which is a major problem when it comes to running projects. And one final thought, it is highly unlikely you will learn anything much from peers... and most likely you will not have time to improve yourself because of above reasons.
Web developer here and used git for last 2 years on a daily basis.
Gitsh looks promising, but I will hold my verdict until I use it for an extended period, and see how it can improve my work life.
Currently I use a combination of SmartGit and Git Bash. SmartGit is mainly used in visualizing branch history, resolve conflicts, tagging and do some odd jobs here and there e.g. edit message of the last commit. Git Bash is used for checking out branches, merging, pulling, pushing sort of stuff i.e. any operation that is more straight forward on the command line, which I happened to feel "clunky" on SmartGit.
Overall, my underline philosophy is, developers should not spend lot of time in version control related tasks, rather should resort to many tools if necessary to expedite it and move on with tackling big problems i.e. features, bug smashing, optimising.
FYI, I work in far east in a country where total population is about 5 million (40% are immigrants).
Recently I have worked for the top news broadcaster in the country to revamp their website. As part of the support duties, I had the pleasure of sitting in their news room. I met a guy there, whose 9-5 duty is to 1) update news organization's official FaceBook account with up to date news updates, 2) Remove any comment with obscene words; sexist or racist remarks; and other comments alike them. He was telling me, he has to act ASAP for any comment that is beyond acceptable levels. Also he was telling me, he received 500+ emails a day questioning or criticising the moderation policy.
On the same work floor, there was another girl doing exactly same work for the Twitter account. And they have to hire 3 people per account to cover the 24 hours a day (this is not including other expenses like travel, F&B etc.). So, it ain't an easy nor cheap operation.
Later on, when we proposed to implement a commenting system to their new website, they were rather reluctant due to the man power need to maintain it. So they opted out with FaceBook commenting within web pages. such that they are not liable for any comments as it is a 3rd party application. (Note: However, we ended up implementing out-of-the-box comment moderating with the FaceBook, such that they could remove comments when necessary)
Here is my story... I work as a web developer at a SME somewhere in far east. So far I have worked in couple of small to large scale Agile projects. And yes, I had company of college interns, developers, senior developers, consultants and architects alike. To be brutally honest, I abhorred my senior's work with a passion. I always pondered how this kind of incompetent, useless people end up handling multi-million dollar worth mission-critical projects.
Based on my so far analysis, this is how I see it:
1. Most of these seniors have survived simply because of a historical reason you might not know.
In my case, most my seniors survived during the 2008-2009 retrench season. Some survived totally through political clout; some by sacrificing their salary and other benefits. So in management's point of view, these are really valuable employees, and they should retain them at every cost.
2. They were there at the right time.
Around the time they were promoted, may be there weren't anybody to around to challenge them. After all the good crop leaves a firm, there is a window for all the sloppy bafoons to inflate their ego, convince management and climb the promotion ladder without much external challenge.
3. They know how to find scapegoats efficiently and effectively pass the buck.
How do I know about this ? I was a victim ! My firm practiced this 'Russian roulette' style of assigning task, such that everyone ends up get to work in every module of a project; or, bugs get assigned to you, even though you never worked on that module before. Most often, these experienced developer's work break down spectacularly, and I am the one brought in to clear their mess; and when I fail to fix, I end up in prison-cell meeting rooms to receive the brunt of senior management. Over the time, these seniors painted this nice picture of me as a lazy, unreliable, incompetent developer. And the funny thing is, most of these code bases, I didn't write a single line of code and I have absolutely no idea what's going inside. And these code bases are poorly documented/commented, making troubleshooting is a mini-IT project it self (call it "reverse engineering feature XYZ")
Sadly for most of us in junior positions, it is an arduous task to challenge the existing establishment. But at least you can dampen or insulate your self from the shocks from these stupidos. Here's what I do:
1. Don't volunteer to amend their codes.
I made this mistake many times as mentioned. Find who originally developed it in your team. If he/she is there, get him/her to work on it. If he is in a different team, ask project manager to bring him/her back. And importantly, if you are taking up these kind of responsibility, have a written understanding with your project manager that "You are doing your best effort to fix the issue, and if it fails, it is not your fault, it is due to poor implementation of the original developer". Stand up for your self ! in corporate world, nobody is there to stand up for you after all.
Trust me on this, "it is good a senior doing a bad patch that temporarily fix the problem and eventually breaks in future, than you failing to do a perfect job in fixing it for posterity"
2. Give seniors a chance !
Don't bother helping them out of your kindness. Let them shoot their own foot. You entering the picture is the biggest disservice you can do to your self, by becoming the dummy they can shoot.
In my current team, I have a tech lead, who was doing an important module. I had plenty of time to help him, as I finished my module early. Instead, I sat down and watched him failing brilliantly and had a silent laugh. Maybe I could have helped him in many ways, but I digressed and let him eat his own dog food.
3. Promote yourself often
I am not very good in this either. But in this world, hardly people pay attention to other individuals. So if there is an opportunity to shine, or talk about your work... just do it! And if management is still deaf and doesn't acknowledge/appreciate your contributions, move to another firm !
1. We are living in the most peaceful period in the entire history. As much as I hate to say this... I am in the opinion "War accelerates innovation". Let's face it, without wars such as WW2 and cold war, most technologies would've either never evolve into the sophisticated stage there right now, or never would've thought of. Until another major war dawns upon us, where contemporary weapons are inadequate for one party to dominate... most technologies will evolve at a slower pace. (at least that's my prediction).
2. Academic research now rewards people who write more papers, not people do genuinely innovative work. I've been in academic research, and I have first hand experience on "publish-or-perish". Most academics I see today, they do research with the mindset "Save my career, family and future first", rather with the noble intention of serving the knowledge sphere. Most research now-a-days geared towards "publication generating exercise"... rather true down-to-earth investigations. I don't think we will return to golden age of research, where funding doesn't demand things like "X number of publications", "Y number of patents" and "business plan to sell million units".
but I've been working last year or so on a large Java based web development project for a news media company. This project had to be built around Spring framework due to the enterprise CMS we have bought from another company is using it.
Not ranting, but giving my honest opinion, I am quite unsatisfied with the overall outcome. Mainly because, development takes quite a long time as every minor change needs maven compiling, which takes ages unless you have a server as your development machine. Even we opted for custom hardware, still servers hangs up quite frequently due to memory leaks and common solution is to allocate more memory. Finally, I find it pretty difficult to get things stable and functional in the staging/production servers, despite things works smoothly on a local machine/development server.
I don't scapegoat Java language. Once discarded some of the idiosyncrasies (let's face it, all languages has it merits and ugly stuff), I think Java is a nice language to write code. But frameworks are bigger culprits in my opinion. Also some of the early architectural decisions made in this particular project were not sound, and now we are paying a massive price i.e. failed to deliver on time, lot of overtime + cheap pizza, no x-mas bonus, no holidays.
How are things in the C# world? any better? any worse?
On a side note: I think it is ridiculous to test OO languages for performance, as they never directly talks with the hardware.
As a web-dev... I work day in day out with CS grads. As an engineering major, what my observation is, they are pretty bad at seeing the "big picture", and more often, very bad team players.
I attended a top-8 Australian university. In the engineering major, the mantra from day one is "be a team player, look at the big picture, plan ahead and well in advance". In my undergrad years, I have done many group assignment, presentations. These kind of activities will train undergrads to horn their communication and planning skills.
As far as my understanding, if you fail to communicate well, be a team player and plan projects well ahead i.e. see the big picture; you are pretty much doomed when you have to work in professional environments and have to handle big projects.
coffee drinkers are more white-collar, sedentary types who read lot of documents either physical ones or on a LCD screen for the most part of the day... and at occasions, under poor lighting. Isn't this the cause of losing eye-sight ??
Personally, I consume reasonable amount of coffee daily basis and I am close to 30 now. So far I can manage reading without glasses. Since 2 years ago or so, I get very tired reading... somewhat an early sign of losing eye sight. Before that, for 10 years or so, I used to study + code... seems all these heavy duty work is paying the price.. not the coffee...
...cynical about a career as a Scientist/Academic Researcher.
IMHO, there is absolutely no legitimate way of quantifying "success of a scientist". It is down to: 1) how a particular study stands the test of time; 2) extended studies that reassures the accuracy of original results, will make the original investigating scientist a true success. Best example I can provide is, Prof Higgs... even Prof Einstein.
All these 'publish-and-perish' claptrap will only do is: dilute the quality of academic research, discourage collaborations, proliferation of academic malpractices/dishonesty, and perhaps drive-away all the truly passionate scientists/researchers-alike from active research in to obscurity.
I finished my PhD last year in EE/CS. Personally, I did enjoy the pain/pleasure of doing research and the campus life in large. However, about half way through my graduate school, I increasingly felt hopeless being a researcher in academia. I went with the good intention of becoming a down-to-earth true-blue scientist/researcher. But the environment I worked was too toxic to keep to my humble wishes. I just couldn't stay there and keep doing research with a clear conscience knowing the academic dishonesty going around, and wrong-doers getting ahead in the "academic rat race" while I am getting scrutinised constantly for not being productive as them. So I did the bare minimum to defend my thesis, and got out on time with a sane mind to start a career in the industry as a software developer.
I regret about my decision in many ways. But I am happy that I do not have to sell-my-soul to cling on to my current position. Plus, I foresee a much better career path now compared to academia (promotions, ability to move to different institutions/career paths); and finally, got decent pay-cheques to enjoy life like I never did before.
I worked with a fair number of CS grads in my current job. Certainly I am neither a rock-star developer, nor the yard-stick to measure their CS theory... I can tell you that half of them have bad habits like: writing spaghetti/un-maintainable code, not testing code for errors/exceptions, rarely documenting what they code, hardly or never clean up the code for optimal performance and pushing un-compilable code to the main branch. At times, it is undiluted agony to work with them.
I have absolutely no idea what they learn at school. But from the information I gathered from a recent intern who worked with me, he doesn't give a s#!@ about coding, and just killing time to join a bank/financial firm. Surprisingly, he didn't know how to debug codes using a given IDE or initiative to pick up that skill.
Increasingly, my team is getting filled with developers from other majors... mostly Engineering grads, instead of CS majors.
I am a regular social drinker, and I have some fair doubts about this study.
I have tried many different beers in their trademark glasses. But regardless the glass, I always stop at 4 (British) pints of regular beer (5% alcohol level) , as that's the absolute limit of liquids I can hold in my body cage.
My answer for "why some people drink too much?".. I think they are genetically able to process alcohol much faster. Also, the colder climate can make you drink slightly more. Or it could be just that, beer is so cheap*
* - I live in south east Asia, and a pint of good beer (say Guinness, Kilkenny, Hoegarden, Leffe... even Heineken) can be as steep as 12-13 US dollars!
I work as a web developer. During my working hours, I regularly open up 10-20 windows (anything from browsers, development tools, documents, etc) for development purpose. I generally like to pin all my app shortcuts icons on the 'start' menu; thus opening up things is a matter of two mouse clicks. But with the so-called-metro style interface, such conveniences have gone down the drain it seems.
As far as my work concerned, I think I will never move to a win 8 machine. IMHO, win 8 is terrible for developers and anybody alike. Sometimes I can't believe why M$ go down this route to marginalize out developers.
Having explained my displeasure, I must admit.. tile window has some advantages. I like the fact that I don't have to launch apps like mail, news, currency converters to see the latest updates. It really saves some fraction of time and system resources.
I RTFA the whole article... but IMO, it has forgot one or two things....
M$ vs DOJ: If you have read daily technology news back in 90s, you might remember how narrowly M$ escaped from a major anti-trust case. Since then, M$ had to play nice with DOJ to avoid getting the worm can re-opened. So it is somewhat obvious M$ didn't work aggressively in taking over other markets in last decade. All the new players, they do not have to answer DOJ for any anti-trust violations. So... new players are very lucky when it comes to approaching new markets.. be it search, consumer media, social networking etc.
At the very heart of the DOJ case...M$ was accused of "locking-in" customers for their products. And now, fast forward to 2012... Apple is literally locking in consumers behind their gardened walls with a plethora of their own hardware and software, Google & FB literally collecting private details from its consumers. Playing the devil's advocate here, I wonder how come they are not scrutinised intensely ?
M$ massive hiring spree: Though I can't exactly remember the figures and fact, I believe M$'s staff count has gone up by few folds since the turn of the century. Though I am not sure what's the reason behind this; but I am pretty sure this is the real reason why wheels started getting off. More staff means more HR to handle them. My best guess for this 'staff head count inflation' is, having lot of cash in bank.
But my overall conclusion is... markets are wide open only for a brief period of time. One can concur that market only during that brief moment. Late comers will always have to play "do or die" battle before totally convert the market to their camp, or die an early shameful death. M$'s biggest issue it seems, not discovering wide open markets to concur like the rest.
Having said all that, during last decade, M$ consumer products have become more stable and secure than in 90s. That's something worth noting.
Also, I would like to see Steven Sinofsky to head the Redmond camp after Ballmer... looking at his track record, I believe he can stop this plunging boat from drowning.
p.s I have to agree that 'management style' in M$ is somewhat deleterious. My software house has this ghastly 6-month review cycle despite being a SMB. In the most recent review, I was accused of not having any initiatives during work by the reviewing HR boss. My sad situation is, my technical boss disagrees with my initiatives. To avoid annoying him too much, and get the team working on one direction; I have learnt to suspend my ideas and just to be a "yes-boss" guy. But would the HR boss understand my situation fully? Personally, I put lot of hours in writing well-polished reliable code. In return, both my bosses are nit-picking on me. IMO, these reviews are good for "failing" employees.. but the rest, why bother.. just throw them free candy or coffee.
Slashdot Mirror
At least for me, the killer feature of PostgreSQL is its procedure language PL/pgSQL. By a fortunate accident, I had the opportunity to write some complicated features (read "calculation heavy") for a web app using PL/pgSQL. Once coupled with triggers, you can just leave everything to the DB to the point, controller has to do nothing except query and return JSON objects to the front. It is so expressive, powerful, efficient and reliable.
I have worked with MySQL, Oracle, MSSQL and as of late MongoDB.
Given a choice, I will always settle for PostgreSQL... it is just so natural to work with.
Why do people keep deferring their journey to pearly gates to meet their maker ?
On a serious note, we have a population crisis!
That's the root cause for every socio-political problems in our time.
I'd rather be excited if academics, medical practitioners, politicians and alike embark on an project to legalize "ethical euthanasia".
I was a dev in a firm that pledged to do things agile/scrum way. However, nobody knew how to do it in the "text book" sense. As you can imagine, it went horribly wrong, especially for large web projects. Same firm, then tried waterfall, similar disaster.
So I conclude, workflow doesn't really matter. If the team you are working is not properly functioning as a team, likely no workflow can help you.
What I call a properly functioning team is a team with members who has a common goal, willing to sacrifice and work hard to achieve it, and willing to help other team members. Unfortunately, most organizations are driven by appraisal systems, which by design down play team work.
I support the motion of *not* calling programmers as engineers.
Starting from the academic point of view, engineering curriculum is far more different than a CS. General undergraduate engineering course comes with number of core modules with the purpose of teaching basic "Engineering Concepts". Furthermore, engineering courses are focused towards "skills training" by range of hands-on laboratory classes, design projects, team projects etc, to learn skills such as see the big picture, learn how to operate instruments, safety, planning etc.; which are a must to function as a professional engineer in industry. Then once in the trade, engineers generally become a member of a professional body e.g. IEEE, IEE, etc. and they are sworn to obey their code of conducts.
Switching gears to my personal story, I trained as an electrical & computer engineer. After a stint in telecommunications industry, I went on to work in web development. I was quite appalled by the way "programmers" think and execute projects in general.
When I worked in the telecoms, I observed that engineers spend quite a long phase in planning before actual execution. In the process, they have to comply range of regulations on telecoms, environment, etc.; and not to forget other concerns such as the commercial interests, backup plans, future expansions, long terms sustainability, maintainability etc. Overall, they consider the "big picture" and do not bog down with just the technical aspect. When it comes to execution, it is generally smooth and trouble free (usually there is a research & trial period before actual execution). Overall, I've seen much more customer orientation and long term view in engineering firms.
When I worked for the software house, planning was considered a "waste of time" (and not to mention, practises like Agile are generally up the anti). And most often or not, you build the roof of the house before the foundation, then figure out how to connect two of them. By and large, there was poor customer orientation. And most damaging of all, lack of concern or thought on long term view of the project and its outcome. I've lived through many cycles of delivering half-baked solutions to client and milking them on the long run to fix those solutions (and in the worst case scenario, making client go bust). If it is a proper engineering firm, they will be sued for such kind of misconduct for sure.
Just my 2 cents.
I worked for software industry in far east -- a small city-state popularly known as 'the little red dot'.
The firm I have served there had the terrible conflict of interest, where development team delivers rotten products to clients, which will be fixed to a barely operational state later by the maintenance team for a hefty price tag.
Developers always had to ship code, regardless how many bugs or security loop-holes in the product. As you could imagine, project timelines are always half of what it should need. Managers are micro-managing to the point, developers have to report progress every 4 hours. As long as half-baked features are there in a barely demonstrable state, project/product is declared complete by the manager, and the senior manager is happy. Otherwise, developers are forced to admit that they were lazy and incompetent.
Still, none of our clients was happy. Some clients even went bust. The only reason why we had a clientele was, they invested too much that they can't do a U-turn. It was frustrating! Despite being registered as an IT service company, we gave middle finger to the clients far too generously and openly.
I have complained through official and unofficial channels (i.e. in meetings with senior managers behind closed doors) about this unethical practices. Reply was, "This is how we work, we don't care about our clients. If you don't like how we work, the door is open for you to leave".
2 months ago, I was fired. Though they have given ã different reason for the dismissal, their hidden message is "You never played by our rules. Just go away".
As long as corporations operate by the mantra "money over all else", nothing would change. Its a dystopian future after all.
I came to software industry quite late at the age of 27. I worked for number of web development project in Java. And I was fired a month ago saying I am "not a good fit for the team".
The team in question is full of fresh grads (and I was the only non-chinese person), who are willing to work 18 hours a day, 6 days a week; tech leads and managers are around my age, and still they can't do a simple project without a major re-write 2 weeks before going live. Since I don't speak fluent Java, I was often look down for being a "non-technical" person. Still, every project I had control, I made sure work flow is optimised, everybody is in same page, requirements were correctly gathered and most important of all, managing client expectations and keep them satisfied.
For the past few weeks, I tried looking for a similar job. Most companies are unwilling to hire someone in 30s. And as someone mentioned above, most Java jobs asks deep technical questions (and trust me, you will never use those concepts in real world). And also, lot of companies do not want to pay my previous salary level even.
Then I tried Business Analyst positions, and most companies turned me down saying "you have no experience in this domain" or "you haven't done UML before" etc etc. Same goes with project management or other possible jobs in tech line.
To be honest, at this point in my 30s, I feel like I am quite redundant in software industry, and my skills are worthless. It is quite hard to change careers, as I do not have experience in other domains like finance, healthcare or education. Looks like future is doomed at this point of time. I just can't emphasize enough to anyone who is willing to land in a tech career.
I don't see much point to be honest.
For a start, telcos these days have very stringent bandwidth caps. For an example, here in Singapore, a 2 year mobile data plan with 12GB/month costs ~USD 200/month. Other than light usage (e.g. browsing, bit of skype and youtube), you can't do much.
And what about power consumption ? how fast can it drain your phone battery ?
The Goat Simulator
Birth control pills meant to control fish population ???
1. Model M keyboard
2. Lenovo ThinkPad X-series laptop
3. Microsoft Ergo series
I completed my PhD in EE/CS 4 years ago. Right after submission, I was unemployed for 6 months and during which time, I applied for 1000+ positions. Only on my 3rd interview, I was offered a junior dev position with minimum compensation in a SME.
Initially, things were good. I paid my bills and was doing many things I couldn't do as as a grad student i.e. going on holiday, fine dining, drinking binges. Work wise, I enjoyed the first year or so learning and coding new languages/platforms.
After a while, I woke up to the fact that my firm has deep problems in terms of work flow and project management. Almost 90% of the web projects we completed in last 3 years were failures. Perhaps I was too naive, I fed them back to the management and highlighted that the problem is with our SDLC and some incompetencies in mid-layer management and tech people. This did not rhyme well, I was kicked out from dev team and transferred to a different department; and my promotion was denied while every other fresh grad was promoted before me.
Overall my experience is, PhD can work against you. For a start, bosses are always intimidated with your superior intellectual brain and over the top communication skills (and don't forget, most bosses will be at your age too). Other aspect is, rest of your co-workers been there or has cut-teeth in corporate politics, so in an event of political power-struggle, quite literally you don't know what to do. Also most firms has no idea what to do with a PhD qualified human resource, let alone having a boss who can manage one. Lastly, not being mastered in some technologies (like Java) can be a disadvantage.
As of today, I'm feeling quite dejected and unappreciated at my firm. Lately I am looking for a new job (preferably something outside IT). I don't know what the future holds for me. As much as I regret taking up above position, on the hindsight, I landed on that position during recession years and helped me to sail through those critical years.
Please don't !
Short answer:
I made a similar horrible mistake... and only now I'm regretting.
Long answer:
After my graduate studies, I joined to a SME, which was supposed to be in between start up and IPO (this is in far east in Asia). Though the company rolls financially, human resources are what I called "Sub-par" quality. Simply because they don't have any real competition, they think they are the best and ignores all other good ideas coming both internally or externally. In addition, there are no standard workflows to handle situations. So working in such environments is analogous to running around with your head on fire. Lately we have done few projects that are, by all means, text-book quality death marches. Finally, as everyone is pretty young (& not to forget, dumb!), it is pretty hard to get them on the same team spirit and work ethic... which is a major problem when it comes to running projects. And one final thought, it is highly unlikely you will learn anything much from peers... and most likely you will not have time to improve yourself because of above reasons.
Good luck !
Web developer here and used git for last 2 years on a daily basis.
Gitsh looks promising, but I will hold my verdict until I use it for an extended period, and see how it can improve my work life.
Currently I use a combination of SmartGit and Git Bash. SmartGit is mainly used in visualizing branch history, resolve conflicts, tagging and do some odd jobs here and there e.g. edit message of the last commit. Git Bash is used for checking out branches, merging, pulling, pushing sort of stuff i.e. any operation that is more straight forward on the command line, which I happened to feel "clunky" on SmartGit.
Overall, my underline philosophy is, developers should not spend lot of time in version control related tasks, rather should resort to many tools if necessary to expedite it and move on with tackling big problems i.e. features, bug smashing, optimising.
FYI, I work in far east in a country where total population is about 5 million (40% are immigrants).
Recently I have worked for the top news broadcaster in the country to revamp their website. As part of the support duties, I had the pleasure of sitting in their news room. I met a guy there, whose 9-5 duty is to 1) update news organization's official FaceBook account with up to date news updates, 2) Remove any comment with obscene words; sexist or racist remarks; and other comments alike them. He was telling me, he has to act ASAP for any comment that is beyond acceptable levels. Also he was telling me, he received 500+ emails a day questioning or criticising the moderation policy.
On the same work floor, there was another girl doing exactly same work for the Twitter account. And they have to hire 3 people per account to cover the 24 hours a day (this is not including other expenses like travel, F&B etc.). So, it ain't an easy nor cheap operation.
Later on, when we proposed to implement a commenting system to their new website, they were rather reluctant due to the man power need to maintain it. So they opted out with FaceBook commenting within web pages. such that they are not liable for any comments as it is a 3rd party application. (Note: However, we ended up implementing out-of-the-box comment moderating with the FaceBook, such that they could remove comments when necessary)
perhaps Shakespeare is the pioneer of this... with his comedy, history & tragedy plays.. e.g. Romeo Juliet
If you watch any Bollywood film today (or last 20-30 years for that matter), it follows similar plot like Romeo Juliet
Here is my story... I work as a web developer at a SME somewhere in far east. So far I have worked in couple of small to large scale Agile projects. And yes, I had company of college interns, developers, senior developers, consultants and architects alike. To be brutally honest, I abhorred my senior's work with a passion. I always pondered how this kind of incompetent, useless people end up handling multi-million dollar worth mission-critical projects.
Based on my so far analysis, this is how I see it:
1. Most of these seniors have survived simply because of a historical reason you might not know.
In my case, most my seniors survived during the 2008-2009 retrench season. Some survived totally through political clout; some by sacrificing their salary and other benefits. So in management's point of view, these are really valuable employees, and they should retain them at every cost.
2. They were there at the right time.
Around the time they were promoted, may be there weren't anybody to around to challenge them. After all the good crop leaves a firm, there is a window for all the sloppy bafoons to inflate their ego, convince management and climb the promotion ladder without much external challenge.
3. They know how to find scapegoats efficiently and effectively pass the buck.
How do I know about this ? I was a victim ! My firm practiced this 'Russian roulette' style of assigning task, such that everyone ends up get to work in every module of a project; or, bugs get assigned to you, even though you never worked on that module before. Most often, these experienced developer's work break down spectacularly, and I am the one brought in to clear their mess; and when I fail to fix, I end up in prison-cell meeting rooms to receive the brunt of senior management. Over the time, these seniors painted this nice picture of me as a lazy, unreliable, incompetent developer. And the funny thing is, most of these code bases, I didn't write a single line of code and I have absolutely no idea what's going inside. And these code bases are poorly documented/commented, making troubleshooting is a mini-IT project it self (call it "reverse engineering feature XYZ")
Sadly for most of us in junior positions, it is an arduous task to challenge the existing establishment. But at least you can dampen or insulate your self from the shocks from these stupidos. Here's what I do:
1. Don't volunteer to amend their codes.
I made this mistake many times as mentioned. Find who originally developed it in your team. If he/she is there, get him/her to work on it. If he is in a different team, ask project manager to bring him/her back. And importantly, if you are taking up these kind of responsibility, have a written understanding with your project manager that "You are doing your best effort to fix the issue, and if it fails, it is not your fault, it is due to poor implementation of the original developer". Stand up for your self ! in corporate world, nobody is there to stand up for you after all.
Trust me on this, "it is good a senior doing a bad patch that temporarily fix the problem and eventually breaks in future, than you failing to do a perfect job in fixing it for posterity"
2. Give seniors a chance !
Don't bother helping them out of your kindness. Let them shoot their own foot. You entering the picture is the biggest disservice you can do to your self, by becoming the dummy they can shoot.
In my current team, I have a tech lead, who was doing an important module. I had plenty of time to help him, as I finished my module early. Instead, I sat down and watched him failing brilliantly and had a silent laugh. Maybe I could have helped him in many ways, but I digressed and let him eat his own dog food.
3. Promote yourself often
I am not very good in this either. But in this world, hardly people pay attention to other individuals. So if there is an opportunity to shine, or talk about your work... just do it! And if management is still deaf and doesn't acknowledge/appreciate your contributions, move to another firm !
I have two points to back up my answer.....
1. We are living in the most peaceful period in the entire history. As much as I hate to say this... I am in the opinion "War accelerates innovation". Let's face it, without wars such as WW2 and cold war, most technologies would've either never evolve into the sophisticated stage there right now, or never would've thought of. Until another major war dawns upon us, where contemporary weapons are inadequate for one party to dominate... most technologies will evolve at a slower pace. (at least that's my prediction).
2. Academic research now rewards people who write more papers, not people do genuinely innovative work. I've been in academic research, and I have first hand experience on "publish-or-perish". Most academics I see today, they do research with the mindset "Save my career, family and future first", rather with the noble intention of serving the knowledge sphere. Most research now-a-days geared towards "publication generating exercise"... rather true down-to-earth investigations. I don't think we will return to golden age of research, where funding doesn't demand things like "X number of publications", "Y number of patents" and "business plan to sell million units".
but I've been working last year or so on a large Java based web development project for a news media company. This project had to be built around Spring framework due to the enterprise CMS we have bought from another company is using it.
Not ranting, but giving my honest opinion, I am quite unsatisfied with the overall outcome. Mainly because, development takes quite a long time as every minor change needs maven compiling, which takes ages unless you have a server as your development machine. Even we opted for custom hardware, still servers hangs up quite frequently due to memory leaks and common solution is to allocate more memory. Finally, I find it pretty difficult to get things stable and functional in the staging/production servers, despite things works smoothly on a local machine/development server.
I don't scapegoat Java language. Once discarded some of the idiosyncrasies (let's face it, all languages has it merits and ugly stuff), I think Java is a nice language to write code. But frameworks are bigger culprits in my opinion. Also some of the early architectural decisions made in this particular project were not sound, and now we are paying a massive price i.e. failed to deliver on time, lot of overtime + cheap pizza, no x-mas bonus, no holidays.
How are things in the C# world? any better? any worse?
On a side note:
I think it is ridiculous to test OO languages for performance, as they never directly talks with the hardware.
As a web-dev... I work day in day out with CS grads. As an engineering major, what my observation is, they are pretty bad at seeing the "big picture", and more often, very bad team players.
I attended a top-8 Australian university. In the engineering major, the mantra from day one is "be a team player, look at the big picture, plan ahead and well in advance". In my undergrad years, I have done many group assignment, presentations. These kind of activities will train undergrads to horn their communication and planning skills.
As far as my understanding, if you fail to communicate well, be a team player and plan projects well ahead i.e. see the big picture; you are pretty much doomed when you have to work in professional environments and have to handle big projects.
coffee drinkers are more white-collar, sedentary types who read lot of documents either physical ones or on a LCD screen for the most part of the day... and at occasions, under poor lighting. Isn't this the cause of losing eye-sight ??
Personally, I consume reasonable amount of coffee daily basis and I am close to 30 now. So far I can manage reading without glasses. Since 2 years ago or so, I get very tired reading... somewhat an early sign of losing eye sight. Before that, for 10 years or so, I used to study + code... seems all these heavy duty work is paying the price.. not the coffee...
...cynical about a career as a Scientist/Academic Researcher.
IMHO, there is absolutely no legitimate way of quantifying "success of a scientist". It is down to: 1) how a particular study stands the test of time; 2) extended studies that reassures the accuracy of original results, will make the original investigating scientist a true success. Best example I can provide is, Prof Higgs... even Prof Einstein.
All these 'publish-and-perish' claptrap will only do is: dilute the quality of academic research, discourage collaborations, proliferation of academic malpractices/dishonesty, and perhaps drive-away all the truly passionate scientists/researchers-alike from active research in to obscurity.
I finished my PhD last year in EE/CS. Personally, I did enjoy the pain/pleasure of doing research and the campus life in large. However, about half way through my graduate school, I increasingly felt hopeless being a researcher in academia. I went with the good intention of becoming a down-to-earth true-blue scientist/researcher. But the environment I worked was too toxic to keep to my humble wishes. I just couldn't stay there and keep doing research with a clear conscience knowing the academic dishonesty going around, and wrong-doers getting ahead in the "academic rat race" while I am getting scrutinised constantly for not being productive as them. So I did the bare minimum to defend my thesis, and got out on time with a sane mind to start a career in the industry as a software developer.
I regret about my decision in many ways. But I am happy that I do not have to sell-my-soul to cling on to my current position. Plus, I foresee a much better career path now compared to academia (promotions, ability to move to different institutions/career paths); and finally, got decent pay-cheques to enjoy life like I never did before.
I am a Electrical Engineer turned web-dev.
I worked with a fair number of CS grads in my current job. Certainly I am neither a rock-star developer, nor the yard-stick to measure their CS theory... I can tell you that half of them have bad habits like: writing spaghetti/un-maintainable code, not testing code for errors/exceptions, rarely documenting what they code, hardly or never clean up the code for optimal performance and pushing un-compilable code to the main branch. At times, it is undiluted agony to work with them.
I have absolutely no idea what they learn at school. But from the information I gathered from a recent intern who worked with me, he doesn't give a s#!@ about coding, and just killing time to join a bank/financial firm. Surprisingly, he didn't know how to debug codes using a given IDE or initiative to pick up that skill.
Increasingly, my team is getting filled with developers from other majors... mostly Engineering grads, instead of CS majors.
I am a regular social drinker, and I have some fair doubts about this study.
I have tried many different beers in their trademark glasses. But regardless the glass, I always stop at 4 (British) pints of regular beer (5% alcohol level) , as that's the absolute limit of liquids I can hold in my body cage.
My answer for "why some people drink too much?".. I think they are genetically able to process alcohol much faster. Also, the colder climate can make you drink slightly more. Or it could be just that, beer is so cheap*
* - I live in south east Asia, and a pint of good beer (say Guinness, Kilkenny, Hoegarden, Leffe... even Heineken) can be as steep as 12-13 US dollars!
I work as a web developer. During my working hours, I regularly open up 10-20 windows (anything from browsers, development tools, documents, etc) for development purpose. I generally like to pin all my app shortcuts icons on the 'start' menu; thus opening up things is a matter of two mouse clicks. But with the so-called-metro style interface, such conveniences have gone down the drain it seems.
As far as my work concerned, I think I will never move to a win 8 machine. IMHO, win 8 is terrible for developers and anybody alike. Sometimes I can't believe why M$ go down this route to marginalize out developers.
Having explained my displeasure, I must admit.. tile window has some advantages. I like the fact that I don't have to launch apps like mail, news, currency converters to see the latest updates. It really saves some fraction of time and system resources.
I RTFA the whole article... but IMO, it has forgot one or two things....
M$ vs DOJ: If you have read daily technology news back in 90s, you might remember how narrowly M$ escaped from a major anti-trust case. Since then, M$ had to play nice with DOJ to avoid getting the worm can re-opened. So it is somewhat obvious M$ didn't work aggressively in taking over other markets in last decade. All the new players, they do not have to answer DOJ for any anti-trust violations. So... new players are very lucky when it comes to approaching new markets.. be it search, consumer media, social networking etc.
At the very heart of the DOJ case...M$ was accused of "locking-in" customers for their products. And now, fast forward to 2012... Apple is literally locking in consumers behind their gardened walls with a plethora of their own hardware and software, Google & FB literally collecting private details from its consumers. Playing the devil's advocate here, I wonder how come they are not scrutinised intensely ?
M$ massive hiring spree: Though I can't exactly remember the figures and fact, I believe M$'s staff count has gone up by few folds since the turn of the century. Though I am not sure what's the reason behind this; but I am pretty sure this is the real reason why wheels started getting off. More staff means more HR to handle them. My best guess for this 'staff head count inflation' is, having lot of cash in bank.
But my overall conclusion is... markets are wide open only for a brief period of time. One can concur that market only during that brief moment. Late comers will always have to play "do or die" battle before totally convert the market to their camp, or die an early shameful death. M$'s biggest issue it seems, not discovering wide open markets to concur like the rest.
Having said all that, during last decade, M$ consumer products have become more stable and secure than in 90s. That's something worth noting.
Also, I would like to see Steven Sinofsky to head the Redmond camp after Ballmer... looking at his track record, I believe he can stop this plunging boat from drowning.
p.s
I have to agree that 'management style' in M$ is somewhat deleterious. My software house has this ghastly 6-month review cycle despite being a SMB. In the most recent review, I was accused of not having any initiatives during work by the reviewing HR boss. My sad situation is, my technical boss disagrees with my initiatives. To avoid annoying him too much, and get the team working on one direction; I have learnt to suspend my ideas and just to be a "yes-boss" guy. But would the HR boss understand my situation fully? Personally, I put lot of hours in writing well-polished reliable code. In return, both my bosses are nit-picking on me. IMO, these reviews are good for "failing" employees.. but the rest, why bother.. just throw them free candy or coffee.