380 karma · joined August 21, 2009
Many years ago, I became the designated maintainer for a legacy inventory system that was used for internal audit purposes. The system ran on a PDP-11/70, and was written in a combination of Basic-Plus (this was a long time ago) and COBOL. I only had a passing familiarity with either of those languages. I find the challenges of learning a code base usually boil down to a few recurring problem areas:
* Problem domain knowledge: The system was used to track leased telecommunication facilities, and had a lot of obscure business logic built into it. At least half the challenge was reverse engineering business logic from the code.
* Coding style: I always find it challenging to get comfortable with another developer's style. Mismatches in assumptions/preferred approaches can make it really hard to get comfortable with someone else's code. This particular system had some truly weird programming choices, including a "screen driver" (similar to curses) written in COBOL.
* Code complexity: I was pretty lucky that the code was not very complicated. With all the other challenges, if the code had been complex it would have probably been an impossible challenge.
* Language knowledge: the original developers had used some features of Basic-Plus and COBOL that were a little obscure, which made understanding the code base that much harder.
Personally, I'm not too concerned about HN karma, but I'm curious about the incentive system that it creates. Does the karma system simply promote adherence to the majority/popular view, or does it improve the quality of discussion?
Also, if you mandate higher costs for suppliers (through limited hours and minimum wages) then you will create incentives for people to buy from suppliers that aren't subject to those regulations (i.e., foreign suppliers). You can try to prevent that through tariffs and duties, but they have their own problems.
1. Most customers choose to buy from the seller with the lowest price.
2. Employees are free to leave their employment if they find the conditions intolerable.
Which of these rules do you want to change?
Gartner also sells research and analysis reports, and subscriptions for these services. These materials, IME, are of higher quality and can be a good introduction or exploration of a particular issue or technology. But they are definitely more oriented toward the senior leader than to the person in the trenches.
"The worry is that this might not be the case for long. Though the housing market has finally recently started to cool, experts tend to agree it’ll tick back upward before long—especially given the reticence of the powers that be to impose the slightest limit on the breakneck pace of growth."
Which are "the powers that be"? City/county/state government? Or large tech employers? Local municipalities do seem to be limiting growth through zoning (a contributor to the high cost of living). If this is to suggest that local employers should somehow limit their own growth, I guess you could point to Amazon choosing to open new headquarters in VA and NY.
I guess I just don't get this paragraph.
I found it interesting that you phrased your interest as "learn workplace politics." From what you describe, it sounds more like this is more an issue of communications and process. I work in the consulting industry, where communications and process are often both critical to successful outcomes.
When I was starting out, I found Gerry Weinberg's books Becoming a Technical Leader, Secrets of Consulting, and The Psychology of Computer Programming to be very interesting and helpful. In fact, in one of them (I think it's Becoming a Technical Leader), Weinberg talks about how an "introvert" may actually turn out to be the more effective technical leader because they focus on solving problems instead of talking about them.
Weinberg also talks about not saying "no" (suggested in another comment), and this is something I've found to be very valuable in consulting. Rather than just telling someone their request can't be done, or accepting it mutely, tell them how much it will cost to do it (Weinberg explains this as the "Orange Juice Test" in Secrets of Consulting).
I do agree with the comment about using wireframes to confirm your understanding/spec with your users. There are other techniques that can also work (e.g., creating user stories with your stakeholders), but the common element is that you must communicate clearly, concisely, and cooperatively with others.
Sorry this comment is a little scattershot, but best of luck with your efforts.
"A Francophone biker in Lennoxville, a Cree lawyer in Manitoba, a Punjabi-speaking business owner on the Lower Mainland, and an anglophone trader on Bay Street may not share any basic ground of identity or culture, but all are, to varying degrees, united by practical bonds of jurisprudence, government, and economics. The novelist’s job is to shed light on the brute fact of those binding forces, and that usually means paying close attention to the institutions and individuals responsible for the country’s current state of affairs."
Personally, I would vote for something by Farley Mowat. ;)
* Remove all the logos/links. They're not helping the first impression, and they'll almost certainly confuse the systems that are used to scan/store your résumé.
* Take out the reference to military technology in your objective. If you get an interview you can ask them if they do military work and explain your reservations.
* Simplify your work history. Try to make it as sequential as possible, with as few gaps as possible. If you have a lot of work experience that is not directly relevant to the position you are seeking, consider changing the format and just list "Relevant Experience".
* Make your education section simpler. Just list your most advanced degree, or include your Bachelor's degree if it is in another field. Don't show your GPA, but include any academic honours you received while obtaining your degree.
* Remove all the icons on the second page, including the flags.
* Condense your charity work/hobbies/extra-curricular activities to a short list. Do list any directorships you held/hold. Don't list specific job titles unless they directly relate to the position you seek.
* You might consider just saying "References available upon request."
Your résumé comes across as kind of "all purpose". Maybe that's just because it's the one you include in your profile. If you aren't creating a focused résumé for each opportunity, you might want to consider doing that.
At the same time, we can say that there is an objective value for labour of a certain type (I'm thinking of commodified labour), which is the going market rate. Just as there is, at any given point in time, an objective value for a share of Apple Computer.
I was also amused by the comment, “I’m very quick to get frustrated when people refuse to pay me what I’m worth.” This seems like a conversation I have at least once a quarter with someone. You're worth what the market is willing to offer you, not what you think you are worth.
2. The problem with any discussion of healthcare issues is that we are naturally swayed by our empathy for those who are suffering. Almost all of us would choose to pay whatever was needed to save a loved one, and would grant that ability to others if we could. It seems simple enough to say "we should spend less money on the military/international aid/tax breaks for corporations/the NEA/etc." if it means that we can provide affordable treatment to those who are suffering. Unfortunately, until the singularity arrives there is probably always going to be a cost that is too high, and hard decisions must be made. As a Canadian, I know that one of the downsides of universal healthcare is that some treatments must be rationed and bureaucrats will make decisions affecting the life of my loved ones. Now that I live in the US I can avail myself of diagnostics and treatments that may simply not be available in Canada. The cost may beggar me and the likelihood of a positive outcome may be remote, but it is my choice, and a choice that may not be available under other systems.
3. No, I have not read all of the comments. As with many HN comment pages, the marginal value of descendant comments seems to drop off quickly.
"A separate study by the University of York in Britain that sought to assess the risks of microplastics to the environment, published Wednesday, concluded not enough is known to determine if microplastics cause harm."
Both comments are expressing opinions that have nothing to do with the content of the article.
Vicar to parishioner: "My word, Mrs. Jones, do you always have twins?" Mrs. Jones: "Oh, no sir, most of the time we don't have anything."
My suspicion is that this study has been presented and promoted as justification for increased taxation of the wealthy. Of course, increased taxation of upper quintiles won't actually change the distribution of wealth unless the government directly transfers the proceeds of increased taxation to those in the lower quintiles. But that won't happen. Instead, the increased taxes would be used to give those in the lower quintiles services that the government has decided they need (or to further subsidize corn farming or other friends of the party in power).
As a thought experiment, I wonder how many people would support a proposal to take the aggregate payroll of their local NFL/NBA/MLB/NHL franchise, and distribute it evenly among all of the players on the team roster. Not many, I suspect.