|
That article can also be read as: "Do not become a business programmer."
|
|
|
|
|
The designers of Go agree with the collective experience of the last twenty years of programming that there are three basic data types a modern language needs to provide as built-ins: Unicode strings, variable length arrays (called “slices” in Go), and hash tables (called “maps”). Languages that don’t provide those types at a syntax level cannot be called modern anymore. (And what’s up with all the languages that claim all you need are linked lists? I’m sorry, this is not 1958, and you are not John McCarthy.) Go strings are UTF-8 because Go was designed by the guys who invented UTF-8, so why not? Everybody's talking about Go this week. What do you think about it?
|
|
|
|
|
Terrence Dorsey wrote: Go strings are UTF-8 because Go was designed by the guys who invented UTF-8, so why not?
You learn something new everyday!
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
"the directory the fundamental unit of packaging"
"this leads to the convention of using domain names as directory names"
The code still has to be stored in the file system? I thought he said this wasn't 1958.
I prefer to be able to have all the code in one directory.
And the ability to have all the code in one file (for trivial stuff at least).
Seriously, we shouldn't need to store code in files anymore.
|
|
|
|
|
Excellent point, I particularly dislike the use of domain names for packages.
I work on some of my own projects, and shouldn't haven't to register for a domain name to follow naming conventions.
|
|
|
|
|
I hear some of you, already. Just when you were over with that mess that it is to manipulate the DOM and that sneaky JavaScript language. Just when you learned to love the highly architected Android classes and managers or iOS’s beautiful method naming, why would we be back to that mayhem that is writing web applications? Didn’t we agree that HTML was not, after all, good enough for making real and performing apps? WebAPI will free you... except for all that pesky platform API stuff.
|
|
|
|
|
Whether you like XML or not, we’re stuck with it for a long time. These days, the only new XML-based projects being started up are document-centric and publishing-oriented. Thank goodness, because that’s a much better fit than all the WS-* and Java EE config puke and so on that has given those three letters a bad name among so many programmers. XML for your document database is actually pretty hard to improve on. <adjective>Happy</adjective><noun>Birthday</noun><punctuation>!</punctuation>
|
|
|
|
|
Terrence Dorsey wrote: <adjective>Happy</adjective><noun>Birthday</noun><punctuation>!</punctuation>
There is an error in XML document:
="1.0"="UTF-8"="yes"
<sentence>
<adjective>Happy</adjective>
<noun>Birthday</noun>
<punctuation>!</punctuation>
<sentence>
|
|
|
|
|
No question that XML is good, but it is also bad, and can ugly. The bad I would say is the it is verbose. Part of probably what should have been the spec should have be a standard for compression. The ugly: comments. Basically the syntax for comments sucks.
|
|
|
|
|
What one Microsoft program or product that was never fully developed or released do you wish had made it to market? Gates: "We had a rich database as the client/cloud store that was part of a Windows release that was before its time. This is an idea that will remerge since your cloud store will be rich with schema rather than just a bunch of files and the client will be a partial replica of it with rich schema understanding." For those who may not know, Gates was referencing WinFS, or Windows Future Storage. ...and other tidbits from Bill Gates' first-ever Ask Me Anything (AMA) on Reddit.
|
|
|
|
|
The problem with putting words like "future" in names is that even 5 years down the road, it seems a silly name. A bit like calling a road "New Road".
=====
\ | /
\|/
|
|-----|
| |
|_ |
_) | /
_) __/_
_) ____
| /|
| / |
| |
|-----|
|
=====
===
=
|
|
|
|
|
Remember new college in oxford, england. There you have several 100 years
|
|
|
|
|
|
If quotation frequency was a measurement of significance, Gordon Moore definitely would be the most important semiconductor engineer in history. Moore's Law – which states the number of transistors in semiconductors doubles every 18 months – has been Silicon Valley canon law for 40 years. However, Moore’s Law has nothing to do with engineering and everything to do with marketing.... While engineering is not a one-man show, it was two engineers at competing companies who led their employer’s respective evolution of the x86 architecture: Pat Gelsinger and Derrick “Dirk” Meyer.... After more than 30 years, the x86 architecture continues to grow, when most technologies go obsolete within a decade. From x86 to x64 and beyond...
|
|
|
|
|
Maybe changed the world, but maybe not for the better. Gelsinger may be single handedly responsible for us being stuck with the 8086 instructions. Still, a very impressive guy.
|
|
|
|
|
Even science recognizes that diversity is important: research from both the Kellogg and Sloan Schools suggest that cognitively diverse teams perform better on hard problems. Beyond that, though, hiring for diversity will set up better recruiting opportunities. Consider Harvard’s graduating computer science class: forty-one percent of the students are women, and an inability to hire talented females will start to significantly impact your ability to recruit altogether. Optimize for "let’s build together" rather than, “let me prove to you how smart I am.”
|
|
|
|
|
While Excel the program is reasonably robust, the spreadsheets that people create with Excel are incredibly fragile. There is no way to trace where your data come from, there’s no audit trail (so you can overtype numbers and not know it), and there’s no easy way to test spreadsheets, for starters. The biggest problem is that anyone can create Excel spreadsheets—badly. Because it’s so easy to use, the creation of even important spreadsheets is not restricted to people who understand programming and do it in a methodical, well-documented way. The role of Microsoft Excel in the “London Whale” trading debacle.
|
|
|
|
|
|
CodeProject wants to help women get involved and build careers in programming. What can we do? We asked some prominent female programmers, and this is what we learned. What we learned about getting more women involved in programming.
|
|
|
|
|
Terrence Dorsey wrote: getting more women
I'm all for it. Where do I sign up?
|
|
|
|
|
Thanks for a textbook illustration of why we have a lot of work to do.
Director of Content Development, The Code Project
|
|
|
|
|
|
One way to be successful is to see how something similar was done in the past. I wonder what industries in the past were lacking women and how the balance was shifted.
|
|
|
|
|
Good point. In fact, that will bring us to an odd conclusion.
In South East Asia there are a lot of women working in construction, roads, railroads. Those are typical 'male jobs' according to western standards. Ironically, nobody is complaining about those jobs having too few women candidates...
Apart from exposing an underlying hypocrisy in the entire story of equal opportunity, it also teaches us that how people fill in gender roles is largely determined by how culture defines those roles.
So, if we want more women in IT, we need to change our culture. Sounds easy, right?
.
|
|
|
|
|