|
Most senior development centers have a greater number of widows on the make. I hear.
|
|
|
|
|
|
Sorry, the company can't afford raises this year. Since you are now 24 years old and have been with us for 2 years now - you are now a senior developer.
|
|
|
|
|
A good article, and one that I've often mentioned to other developers. Length of service is no substitute for knowledge gained. Working at one company on the same product on the same code base is no substitute for having worked with different methodologies, architectures, languages etc.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Dominic Burford wrote: Length of service is no substitute for knowledge gained.
It depends how you think of it..
If you compare it to a prison sentence for example, then length of service (time done) is very important. How many heads you've cracked, tattoos you've got, how many members in your crew - it all makes a difference.
See, exactly like programming! 
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
In that case, I take it all back
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
I disagree with the take on books.
You get sites like pluralsight, codeacademy, etc that are specifically to learn from. I don't even use books for reference anymore because it's faster to refer to other projects, hit stackoverflow/cp, etc.
I think books are ok for people who learn that way, but not everyone does. I learn much faster/better from video tutorials or live interaction. Books for tech are at the bottom end of the resource list. Though I do read a lot of tech material online, but not books so often.
Elephant elephant elephant, sunshine sunshine sunshine
|
|
|
|
|
Personally, I think he's referring to how people go to sites, and go with whatever they find and stick it in. They know WHERE to find the answer, but they may not know what it means, or how to properly use what they are given. In a book, you learn more in-depth about HOW something works, and not just that it does.
Tech material would be the same as a book IMHO, it's just shorter and more concise than most books. Video tutorials and live chat is good if you find a reliable resource.
|
|
|
|
|
I get the Senior Discount on Wednesdays and Thursdays at Goodwill now!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
It means that I have the experience to tell you that duck-typed languages and all those "methodologies" cause more problems than they're worth, but it also means that I don't have the patience to hold your hand and explain in simple single syllable words why.
Marc
|
|
|
|
|
On a serious note; I'd observed that at the very least, you must have at least 7 years active experience in a given technology.
|
|
|
|
|
One of the most [relics from old versions of Windows] annoying is the environment variables dialog. This box hasn't been updated for what feels like millennia, and it's cramped and awkward to use as a result. Environment variables can be lengthy, and they almost never fit in the current dialog. This is particularly acute for one of the most important variables, PATH. The PATH variable stores the names of all the directories that the system should search when hunting for executables, and many applications and development tools like to add their directories to the PATH. It quickly gets unwieldy.
But the newest Insider build of Windows 10 shows that this unloved corner of the operating system has finally received some attention. The environment variables box has been reworked: it's now resizable so you can see the variables in full, and it contains better editors for each value.
Even more usefully, the PATH variable has special handling. The dialog knows that a PATH is made up of a set of directory paths and lets you edit them all individually instead of making you treat them as one single piece of text.
Finally a compelling reason to upgrade. (Once this makes its way from preview to release anyhow.)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
' bout freakin' time!
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
I just use this app now.
http://www.rapidee.com/en/about[^]
I takes a few minuets to get used to but it makes it quick to find bad variables or to just add or update them, including the order for multiple in one section.
|
|
|
|
|
Dan Neely wrote: Even more usefully, the PATH variable has special handling. The dialog knows that a PATH is made up of a set of directory paths and lets you edit them all individually instead of making you treat them as one single piece of text.
They've only had this "advanced" technology in Visual Studio since version 6 (IIRC). Makes you wonder what tools are being used by the Windows group.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I was going to say that.. I've NEVER had a problem changing the PATH since it's in VS..
|
|
|
|
|
ARIN has assigned the last of its free pool of fresh IPv4 addresses Buddy, can you spare a C block?
|
|
|
|
|
That is good News! It will force ipv6 
modified 19-Jan-21 21:04pm.
|
|
|
|
|
If people still sticks to VB6 legacy softwares... do you really think they will upgrade to IPv6???
That's gonna be fun
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Tunnels. Because rewriting software for no good reason is plainly dumb.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
"When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
|
|
|
|
|
Google's IPv6 report[^] puts it at about 7.5%; zooming in shows it at barely over 7% during the week and nearly 9% during the weekend. Per country data shows that most of that's coming from a handful of countries with Belgium (36%), Switzerland (23%), and the USA (21%) leading the pack for trouble free adoption. Germany appears to be in 4th place at 18% adoption; but suffers a 20ms latency penalty for IPv6 usage.  Portugal (16%), Peru (15%), and Greece (11%) round out the >10% club; but only the first of the trio has a problem free experience.
The Greek situation is disappointing; if they had their stuff together and went all IPv6, they'd be able to sell almost 5 million addresses. And while $50 million is a drop in the bucket compared to their total debt problem, it's not like they're having any success elsewhere selling stuff off to pay it down. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Dan Neely wrote: The Greek situation is disappointing; if they had their stuff together and went all IPv6, they'd be able to sell almost 5 million addresses. And while $50 million is a drop in the bucket compared to their total debt problem, it's not like they're having any success elsewhere selling stuff off to pay it down.
And how much would it cost them to make the changeover? I'll bet that it's a lot more than $50 million.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
If #NoEstimates is the answer, what was the question? How about: it will probably be done before the heat death of the universe?
|
|
|
|
|
In the course of writing the proposal, I worked out a cost estimate for the software.
This is fine.
Perhaps "no estimates once the project is in flight that can be then used as a stick to beat developers with and cause a cycle of distrust that can destroy a functioning team dynamic" ... but that's a bit long for a hash tag.
|
|
|
|
|
Realistically (based on my esteemed experience) estimates and agile are orthogonal. The specs are usually so loose, the design so vague, the what-if's so undefined, that estimates in terms of concrete hours is useless.
Instead, estimates should be made as a percent of the scope of the entire project, which is artificially introduced as 100% = some time span, say a year.
Then, you estimate all the parts as a percentage, making sure they don't total up to more than 100%.
Now, when your project scope balloons, which it will because you are agile, what you do is add to the total time. Now, all your % estimate pieces (even the ones you've completed) suddenly have gained more time, which of course gets easily sucked up refactoring existing and writing new unit tests, because of course, you've hobbled the whole concept of Agile by forcing yet another discipline orthogonal to real progress, Test Driven Development.
But the point being that software creep no longer becomes an estimation of the new features and therefore extends the time to deliver, it is instead a % increase of all features in the entire project.
Anyways, that's how I now estimate an agile project. Actually, even if you don't do agile, I think that's a much more effective way of estimating scope changes.
Marc
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
