We've since switched to GeoTab and a BYOD model. The GeoTab devices are a lot cheaper, so a contractor walking away with one isn't that big of an issue. Rollout was much smoother this time.
1,867 karma · joined March 12, 2013
We've since switched to GeoTab and a BYOD model. The GeoTab devices are a lot cheaper, so a contractor walking away with one isn't that big of an issue. Rollout was much smoother this time.
I've found this EDI notepad useful for parsing flat files: https://www.liaison.com/products/integrate/edi-notepad/
And this npm library actually parses EDIs pretty well too: https://www.npmjs.com/package/x12
An example 204 EDI (Load Tender) looks like this:
ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*SM*4405197800*999999999*20111219*1747*2100*X*004010
ST*204*0001
B2**XXXX**9999955559**PP
B2A*04
L11*NONPRIMARY*OK
MS3*XXXX*B**M
NTE**FROZEN GOODS SET TO -10d F
N1*PF*XYZ CORP*9*9995555500000
N3*31875 SOLON RD
N4*SOLON*OH*44139
N7**NONE*********FF****5300
S5*1*CL*27800*L*2444*CA*1016*E
L11*9999001947*DO
L11*9999670098*CR
L11*9999001866*DO
L11*9999669887*CR
G62*69*20111218
N1*SH*XYZ CORP*9*9991555550000
N2*TERMINAL FREEZER
N3*5555 TERMINAL RD
N4*CLEVELAND*OH*44023
S5*2*PU*3042*L*312*CA*146*E
L11*9999001866*DO
L11*9999595358*PO
L11*9999669887*CR
G62*70*20090728
N1*ST*1 EDI SOURCE*93*9990055555
N3*31875 SOLON RD
N4*SOLON*OH*44139
OID*9999669887*99999595358**PC*312*L*3042*E*146
L5**FREIGHT
G61*IC*FEEDBACK*EM*FEEDBACK@1edisource.com
S5*3*CU*24758*L*2132*CA*870*E
L11*9999001947*DO
L11*9999008881*PO
L11*9999670098*CR
G62*70*20111218
N1*ST*1 EDI SOURCE*93*9990055555
N3*55555 5TH AVE
N4*MAYFIELD*OH*44244
OID*9999670098*999608881**PC*2132*L*24758*E*870
L5**FREIGHT
G61*IC*FEEDBACK*EM*FEEDBACK@1edisource.com
L3*27800*G*******1016*E*2444*L
SE*46*0001
GE*1*2100
IEA*1*000002104
I haven't proper parsed it, but I believe that's going from Cleveland to Mayfield. One of those L11 segments is probably a reference number. There's no MS1 segment so it's likely over the road? Anyway, it's not exactly descriptive or even human readable...A reply accepting a load looks like this:
ISA*01*0000000000*01*0000000000*ZZ*ABCDEFGHIJKLMNO*ZZ*123456789012345*101127*1719*U*00400*000003438*0*P*>
GS*GF*4405197800*999999999*20111219*1742*000000003*X*004010
ST*990*000000003
B1*XXXX*9999919860*20111218*A
N9*CN*9999919860
SE*4*000000003
GE*1*000000003
IEA*1*000000003
These are commonly exchanged as text files over FTP sites.Some of our more forward-thinking, larger customers are considering moving to AS2, which I believe is sent over HTTP vs FTP. A cursory Google search doesn't really turn up any clear examples on AS2, which doesn't exactly comfort me, but at least there's an RFC[0] for it, whereas for the X12 spec you have to pay[1] to see certain parts of it.
Not that anyone follows the "spec" anyway. We code special handling for every single one of our customer's EDI transmissions.
I wish everything was REST, or at least JSON. That would be 10x easier. Instead we spend weeks going back and forth on silly things like what a 07 means in the ATS segment, or what character to use for line endings (wish I was kidding -- we've been blocked for two months on the line ending character).
What's more is with the ELDs in all our trucks, customers are increasingly wanting GPS updates. I'd love to offer them a streaming socket with GPS data -- it's completely feasible considering our ELD backend. Instead everyone is wondering how we can send updates in 15 minutes increments over FTP, especially when these transactions are often batched in 5 minute loops on both ends in the first place.
It kills me a little. We could be doing so much more. I can't believe we aren't pushing for real time. I can't believe five to fifteen minute batching loops are acceptable.
[0]: http://www.ietf.org/rfc/rfc4130.txt [1]: http://www.x12.org/x12-work-products/x12-edi-standards.cfm
Especially with the recent push by the fed to put electronic logging systems in every truck, this system is absolutely ripe for disruption. Downside is you'll be fighting entrenched companies like IBM for ground.
Show me a better system instead.
Umbrella Note is a whopping 78mb versus Evernote at 129mb. I'm not sure "another copy of Chromium" is a big deal. I'm not sure what you're talking about in regards to the bloated markup. Are you referring to HTML and CSS? I'm also not really of the opinion that a simple note taking app needs to be multithreaded. This would increase complexity in any language.
My first thought when looking at this project wasn't "oh no Electron!" My first thought was "I could actually contribute to this project," because I, like many many others, use and understand what is likely the most prevalent programming language in the world.
I've found I end up looking at the comments frequently and just hoping that someone was kind enough to plainly explain the grammar at some point. Failing that, I end up asking fluent Spanish speakers random questions like, "Are adjectives gendered and pluralized in Spanish?" Which works up to a point, but when you start asking about things like "gerunds" and "past participle" you end up having to explain what those things mean in the first place (using English) and then ask the question again about Spanish.
Would love to see an app that focuses less on implied methods of teaching and is more willing to dive in to grammar lessons.
That's not how it works. Anything above $200,000 will be taxed at 35%.
You're taxed in brackets. For the first $9525 you're taxed at 10%, from $9525 to $38,700 you're taxed at 12%, and on we go.
Your actual federal income tax at $300,000 is going to be more like $80,000. California state income tax is the same way, and the 13% doesn't appear to kick in until you're above a million [0], so that's more like $25,000, for a total of $106,000ish[1].
You "simplified" $44,000 away.
[0]: https://www.tax-brackets.org/californiataxtable
[1]: I'm really bad at my taxes, so take that number with a grain of salt, but it sure as hell isn't a flat $150,000.
Hope it takes off. Such an awesome name and simple format.
From the medium to enterprise range, maintenance and stability issues are often one in the same. Breaking automated maintenance and/or deployment leads to instability.
Keep in mind I don't mean "kernel panic" levels of instability or even "programs crashing" levels of instability. The smallest of changes can cause a mountain of work in large environments. Simply changing the icon of an often used program can cause a deluge of tickets.
This level of stability and control is something that macOS doesn't even come close to recognizing.
Windows has provisions for performing all sorts of tasks across a fleet of desktops. I can automate deployment of a Windows desktop to the point where all you have to do is boot it up and join it to the domain (which makes it easier to hire someone to do it as well).
What's more is that these settings will work across updates. I've gotten really sick of the screwy changes Apple makes to macOS with little warning. Windows goes to great lengths to ensure backwards compatibility between major version upgrades. (For example, did you know VB6 apps still run just fine?) Also, I can get fine grained control of updates to Windows.
But maybe most importantly, I can virtualize Windows and create a virtual desktop environment. Now I can hand out toasters to users and they can just log in to their box from anywhere.
Windows is simply much better at making desktop units fungible.
So I gave up and asked if I could start coming in at 9am instead. Never felt better.
The world can be surprisingly adaptive sometimes.
US student loan debt is somewhere around $1.4 trillion. For comparison, mortgage debt is somewhere around $8.9 trillion. That's a pretty damn big market. [0][1]
If that education was free, I'd wholly agree with you that it's simply our society deciding this is for the betterment of all. But when you combine these two sources of debt (student loans so we can get jobs that afford us home mortgages) then we're looking at a new, weird, first-world form of debt bondage. [2]
Again, I realize that's a very pessimistic point of view. Will be interesting to see how the history books view it in years to come.
[0]: https://en.wikipedia.org/wiki/Student_debt#/media/File:Stude... [1]: https://www.marketplace.org/2018/02/13/economy/divided-decad... [2]: https://en.wikipedia.org/wiki/Debt_bondage
Oh the things I would build...
Had it been Hillary, I don't think there would've been this kind of outrage. She was the "obvious" choice for president. It would be hard to believe a story about Chinese hackers since she didn't need that kind of help anyway. If it did come out that there was some kind of foreign influence, it would've been much easier to downplay it as negligible since the election of Hillary wouldn't have been much a surprise.
I use tabs in vim because opening more than 2 buffers on my laptop gets really crowded.
If two business processes interact through a spreadsheet, or more than two people edit, you're going to immediately run up against the rough edges. Multiple people editing the same sheet inevitably ends in error. It can take a really gross amount of time to update the data when you're pulling/pushing from two sources. It may seem small on the surface, but even 2 hours a week adds up to nearly 3 weeks of work over a year. Can you replace this spreadsheet in 3 weeks?
I've seen this play out many times at large and small scale. The first example that comes to mind is a 10-hour day trip my wife took to go out of town and manually update a whiteboard because somebody messed up the shared spreadsheet. She was very unhappy, and this wasted a precious day during a _very_ busy period. Initially, the whiteboard and spreadsheet worked great, so they didn't "fix" it. It didn't scale to the busy times and really screwed them over.
At a much smaller scale, I wrote a quick SQL query to get some business metrics for the CEO. He asked if I could run it for him every week. Since I didn't have a good place to put this query, I just ran it manually and emailed it to him at first. Then he wanted to share it with someone on the opposite coast outside our network, so he asked if I could start putting it in a shared spreadsheet. My initial thought was to bang out a page they could pull up instead, but I figured it wasn't worth it. Then he wanted another metric. And another that required a bit of logic that couldn't be done in SQL. Pretty soon I was spending an hour a week manually running SQL and copying the results in to a spreadsheet. (We're a Google Drive shop. No way to connect Sheets to DB2.) That's simply not worth my time. I should've listened to my first instinct.
The initial investment in a spreadsheet isn't large, but the ongoing maintenance can really rack up hours. I think it's very often worth investigating any spreadsheet that users have been maintaining/recreating for more than a quarter.
Which is probably why he's had such a hard time explaining it in the first place. Lots of people aren't going to take the time to actually read and understand the situation.
A little bit of this is understandable. You can't wait for every task to get put in to the backlog and planned out in sprints or whatever. But if you've ever had a week where 90% of your time goes to everything but planned work well... it's really frustrating.
There's often a high cost to context switching for developers. There's been some loose "studies" done that confirm this, and I definitely feel it at a personal level. A "quick request" isn't just the half hour it takes me to do the thing. It's the language switch, the environment switch, forgetting what I was in the middle of, etc, that really causes the bulk of my productivity loss.
It gets to the point sometimes where I give two time estimates: one where I'm allowed to shut my door and work, and one where I factor in the likely torrent of interruptions that will more than double my actual completion time.
Edit: Switched my console URL from east to west and it loaded up fine.
I still want to like MongoDB, I still miss its style of query vs SQL, but I'd have a hard time advocating its use again...
Sometimes it's tempting to use it for projects that I know will remain small, but even then it's not worth the overhead of standing up a different DB when I have a perfectly good SQL server I can muddle through already.
If you don't like DI and you're using C#, you're gonna be swimming upstream. It's been the C# dogma for many years. You sound like you'd be much happier away from C#.
I'm currently in a situation where I'm on the fence about two different ways to access my database (both are terrible options). Both db drivers are very different, and require very different code. However, they both return the same models. By defining an interface and injecting one service or the other in to my controllers, I can quite effectively and painlessly switch between the two. Why not a singleton? Because with one of the drivers it's better to build a new one on every request.
Back to injecting configuration... I actually use this database access service across two different ASP.NET Core projects. The configuration manager has a nice way to extract only parts of the configuration in to a model. Combine with DI and I can easily split my configuration models between these projects without a shared config model.
Sure, there's other ways to skin the cat. I'm not saying DI is the only way, but I do find it an effective method and certainly not a "nasty language hack".
We're constantly talking about the Pareto principle: "80% of software can be written in 20% of the time." And we optimize for building that 20% of the code in the simplest, fastest way possible.
The problem is the other 80% of the code, the part that accounts for 20% of the features, ends up being necessary before full adoption of the software takes place. 80% working simply isn't good enough. But since we've optimized for that easy 20% using low-code solutions, the other 80% of our code ends up being twice as painful. We end up deciding it's too expensive to continue and attempt to force use of the 80%-finished software as-is. Historically, this hasn't turned out well for us, and users end up compensating via spreadsheets or even paper.
It takes a couple years for this whole process to play out. The project is often declared a success since 80% of it got done and deployed so quickly. But there's always those last nagging bits that, upon further inspection, have led to the app/feature/whatever being abandoned later on.
> It is that kind of thought process and default overhead that is leading companies to conclude that software development is just too expensive.
It is too expensive for them. If you're building a house and get sticker-shock at the cost of building the foundation, maybe you're in too deep.
Please don't skimp on the foundation.