|
Hit me up if you have questions. I check back at the article periodically but i don't get notified when there are new comments there. The best place to find me is in the lounge, tbh
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
var lex = LexDocument.ReadFrom(filename);
var cfg = CfgDocument.ReadFrom(filename);
var tokenizer = lex.ToTokenizer(cfg.FillSymbols());
var parser = cfg.ToLalr1Parser(tokenizer);
that's not that bad for creating a LALR parser and tokenizer from a PCK spec at runtime
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I've used a dictionary keyed by dictionaries once.
I had to take a shower afterwards.
How's that on a scale?
|
|
|
|
|
that's pretty good. Conceptually i view dictionaries as indexed groups most of the time. In fact, half the time i use dictionaries they have a collection as the TValue member, never mind the key, so they're a fancy collection with an index affixed to it that i use for grouping. In SQL a dictionary is a GROUP BY call.
So I can definitely see using one as a key.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Hmm. I use this:
Dictionary<Token,Dictionary<Token,Value>> a lot. Now that I look at it, yours is a lot more perverse.
Software Zen: delete this;
|
|
|
|
|
but where's your LALR(1) parse table? 
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
This is the last post I read from you. The fact that you use words or alogrithms that I do not understand plus the fact that they seem so evident to you makes me feel real dumb. 
|
|
|
|
|
You think they're evident to me LOL. I understand them about as well as you do. The trick is to practice the ability to code things you don't understand. That way you don't have to be smart.
Duh. 
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I only code things I understand, that's why I stopped coding ten years ago . Today, too much patterns, too much languages, too much frameworks, too much resources. It is less fun - and yes, I am starting to talk like an old fart.
|
|
|
|
|
When I got old and crotchety i stopped using other people's code in my apps *except in UIs*
If I need some big functionality, like drawing graphs of state machines, I'll use a 3rd party tool like Graphviz from my code, but I run the damned executables and capture input and output rather than trying to integrate their API directly.
I don't like other people's code, and I know other people don't like mine.
I like what other people's code *does* sometimes. So if i use it, it's usually behind a "firewall" of being a totally separate app automated by my code.
None of this is professionally practical of course. I'm out of the field though so I can do what i like!
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I told my boss I quit last week, so in one or two weeks I'll be officially out of a job.
I was planning on building my own business, which I've done part time for the past year.
I'm trying to get some projects and customers and so far I've been doing pretty well, sort of by accident because some clients came to me.
And if that doesn't work out I was thinking of going freelance (and possibly have both).
But now I've got a really interesting offer to work for an employer again.
The company is interested in meeting me and I'm certainly going to give them a call.
So then the question arises...
Do I want to build a business and/or go freelance or do I want to be employed?
Both have pros and cons and I'm really not so sure what I want 
|
|
|
|
|
Employment: you have a lot of idle time and/or boredom and a guaranteed regular paycheck.
Freelance: you have a lot of idle time looking for work and panicking about the next payday.
Going into business yourself: You have absolutely no idle time (or life for that matter) and are constantly panicking about the next payday.
|
|
|
|
|
Employment: Steady income.
Freelance: Less steady, but much higher income.
Going into business yourself: Possibly no income at all, but also the only possibility to become filthy rich while others do the work for you 
As I said, pros and cons to all 
One of the pros that makes me seriously consider the employment job is the ability to learn from coworkers and grow into a multinational company.
|
|
|
|
|
Marc Clifton wrote: Employment: you have a lot of idle time and/or boredom and a guaranteed regular paycheck.
Something I just learned, I've been unemployed my whole life. 
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
having a business can be rewarding but there are so many hidden costs and so much hidden labor it's a huge risk even before taking into account a flighty clientbase.
You also have to be salesperson, dev, accountant, PR point and somehow find time for all that while doing QA as well.
Or you can hire, which means regulations, SS payouts, etc.
Subcontracting is a bit easier in that case.
But I don't know. If you've been doing it for awhile and have the inertia then maybe run with it. The sky is the limit, unlike working for someone else.
On the other hand, a little security is nice. And not having to manage all the details.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: You also have to be salesperson, dev, accountant, PR point and somehow find time for all that while doing QA as well.
This.
IMNSHO, if you love to code and want to code for a living, go work for somebody else. If you don't mind spending the majority of your time doing things other than coding (because don't kid yourself, this is what you're going to end up doing), then go ahead and be self-employed.
Personally I've always worked for others for this very reason.
|
|
|
|
|
I do love to code, but I don't hate the other parts either.
Except maybe sales, which is a bit of a problem if you're trying to build something
The feeling when getting a new customer is pretty good though 
|
|
|
|
|
after all the [mostly employed] people scaring you off going it alone the business/freelance hybrid is quite a natural fit.
you can pick up a gig as a freelancer, but then if there's follow-up opportunities you can pitch it through your business: often when you're friendly with the people contracted to they will sometimes ask "do you know somebody who can do this or get that..." they'll often ask you before going back to an agent, guess who their new agent is? if you need people to help you, use other freelancers / contract part timers as much as possible, saves all that employment benefit stuff.
the record keeping is not that much harder than freelance, same rules, document and keep everything. likely you already have an accountant [in mind], find out if they have a preferred package, get a copy or access and bang the info in for them (you'll save on their fees for data entry and probably pick up a feel / opportunities for doing some of the simpler reporting yourself - saves more.) dunno why everyone is scared of accounts, it's the easiest mathematics and there's cheap / online packages that can do the allocation & reporting for you.
yes it's true business is 24/7, last thing you think about before you sleep, first thing you think about when you wake up, good days and bad days, but at the end you're totally in control. ever been in a company going tits-up and wondered why they don't do this or that, don't listen to your suggestions... well guess what, if you see an answer no ones going to tell you to go away mind your own business because, well, it IS your business.
sometimes you'll feel like you have no money, but should you need anything, new equipment, car, clothes you'll just go out and get it because somehow those things take care of themselves. (in fact having money is sometimes a bigger worry than not because you'll have to about pay tax, but spend it on the business and that goes away - which is better? giving that money in return for an asset or giving to the government and getting nothing but a receipt in return?)
finally job opportunity: if they really want you it's your turn to become the hirer, "sounds like a good project, if you were to offer it to my business I could start next week." (never say today/tomorrow).
(also doing that completely removes HR from the process. HR, totally clueless about what you are expected to do, their first task is to scare and dominate the new hire into believing how small you are [and how powerful HR is], that you are the last in so will be first out, that you are on probation so don't bring in your photos and pot plants till HR (dead wrong) confirms you, that you're expected to report daily at like a trained lap dog... on an on, regardless of skill level HR treats you like the most junior of newbies and HR is watching you like you were a 2 year old kid and make you believe HR (dead wrong again) can kick you out with the flick of their pen... forking idiots, got to dominate the staff while fresh so they remember who is the boss - well it's never HR, HR is a service department and has no power ever ... sorry, I go on, I really despise HR.)
anyway I say follow your dreams,
when you're young:
- should it go wrong you can still recover (and when old likely something you'll laugh about)
OTOH when you're old dreams you didn't follow ALWAYS become regrets and make you miserable
Message Signature
(Click to edit ->)
|
|
|
|
|
lopatir wrote: the record keeping is not that much harder
I'm lucky to have a mom who's a bookkeeper, so she helped me keep my books this past year.
I did it all myself, but I've regularly called her like "does this money go here or there in the books?"
Keeping track of your incomes and expenses isn't the hard part, the hardest part is what you should declare when and where on what form.
lopatir wrote: I really despise HR
I never had to deal with (actual) HR.
Only guys who also did the occasional HR thing like whatever it is HR does because HR wasn't really a thing in those companies.
I don't know where you're from (Singapore?), but perhaps HR is different there than in the Netherlands?
The only thing I've seen HR do in a company where I was contracted, was mess up vacancies, like spice it up with utter nonsense because they thought it would be more appealing to programmers.
In any case, employees in the Netherlands are protected by various laws, like you can't just fire people (especially not on the spot, unless you have criminal evidence), you can't set them back in salary, you have to keep paying them even when they get sick (up to two years or something), and lots more.
lopatir wrote: giving that money in return for an asset or giving to the government and getting nothing but a receipt in return?
The eternal struggle!
Do I buy these two quite expensive monitors that I really don't need, but for which I get a tax exempt or do I keep my money and give half to the government, making the difference rather small? (spoiler, I bought the monitors and I love them)
lopatir wrote: should it go wrong
I doubt it will, I'll always have some income and if it really fails I'll always be able to go back to being employed.
I'm young, but I've spread my risks and already kind of build something for myself.
So actually, it could fail, but I'd never really need to recover, perhaps I'm just winning less
lopatir wrote: anyway I say follow your dreams,
Well, that's the hard part.
Is it my dream (right now) to build a company, or is it my dream to learn from great coworkers and have plenty of spare time on the side?
I now have opportunities for good jobs, but I'll always be able to build a company
Thanks for the advice though, they're all words of truth and wisdom
|
|
|
|
|
If you enjoy coding then either work full time or contract your services out.
Running your own business wastes a heck of a lot of good coding time on other, much less interesting and totally unrewarding stuff.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Forogar wrote: much less interesting
I find the bookkeeping pretty interesting actually!
Not something I like doing a lot (but for now it isn't a lot), but I've learned a lot from it
Forogar wrote: totally unrewarding stuff
You'll get a feeling of accomplishment
And, if you do it right, a sh*t ton of money
|
|
|
|
|
|
Ha! That's why I prefer to fly myself and don't leave all the fun to some microcontroller. One main rotor and one motor ought to be enough for everyone[^].
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Why did do handstart? not being very clued in with Radio Control Choppers
|
|
|
|
|
That was not really a hand start. He probably just made sure that the rotor did not get banged up in transport and moves freely. Also, the motor is probably a little stronger and can deliver quite a kick when it's started too abruptly. Newton's third law. When the rotor already is turning, you can go easier on the throttle and give the tail rotor time to compensate for the sudden momentum at the rotor shaft. Noobs often manage to turn around the helicopter 180 degrees by starting too abruptly before the tail rotor has a chance to compensate.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
